Bug 117387 – ccm upgrade does not maintain ordering of Java & SQL scripts

Bug 117387 - ccm upgrade does not maintain ordering of Java & SQL scripts

Summary:	ccm upgrade does not maintain ordering of Java & SQL scripts

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Web Application Framework
Classification:	Retired
Component:	installation (Show other bugs)
Sub Component:
Version:	nightly
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Justin Ross
QA Contact:	Jon Orris
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	113496
	Show dependency tree / graph

Reported:	2004-03-03 10:25 EST by Daniel Berrange
Modified:	2007-04-18 13:03 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-04-06 10:43:43 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Daniel Berrange 2004-03-03 10:25:48 EST

Description of problem:
The Java portion of the upgrade process will typically require that
the SQL schema upgrade has already been done. There may, however, be
cases where there needs to be mulitple java/sql upgrade passes
interleaved. THe ccm upgrade command currently mindlessly runs

   1. All Java scripts
   2. All SQL scripts.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Write an upgrade containing multiple SQL & Java scripts

Actual results:
All Java scripts are run before all SQLK scripts

Expected results:
All scripts are run in the order defined in the .upgrade XML file.


Additional info:

Comment 1 Justin Ross 2004-03-03 13:37:29 EST

Oh right, this is quite broken (it's the cause of the core and cms
6.0-6.1 upgrade problems).  Making this a blocker.

Comment 2 Justin Ross 2004-03-04 12:52:05 EST

Fixed at perforce change 41041.

Note You need to log in before you can comment on or make changes to this bug.