I committed a change to trunk that will make reorg only run on DB2
installs with a major version >= 9.
Nathan
-Original Message-
From: tomnguyen [mailto:tomn...@yahoo.com]
Sent: Friday, March 06, 2009 1:43 PM
To: liquibase-user@lists.sourceforge.net
Subject: Re: [Liquibase-user] RE
Hi Nathan,
I guess you don't need the REORG command in v8 for the simple fact that it
does not exist yet.=^D
tom nguyen
--
View this message in context:
http://www.nabble.com/REORG-function-for-an-addPrimary-tp22336059p22379226.html
Sent from the LiquiBase - User mailing list archive at Nabble
riday, March 06, 2009 11:53 AM
To: liquibase-user@lists.sourceforge.net
Subject: Re: [Liquibase-user] RE ORG function for an addPrimary
Now I understand.
It is because I use DB2 v8.2, which does not have the REORG command
(only in
v9).
This is what is generated:
ALTER TABLE AWS_ATTRIBUTE ADD CONST
Now I understand.
It is because I use DB2 v8.2, which does not have the REORG command (only in
v9).
This is what is generated:
ALTER TABLE AWS_ATTRIBUTE ADD CONSTRAINT PK_AWS_ATTRIBUTE PRIMARY KEY
(PJ_ID);
CALL SYSPROC.ADMIN_CMD ('REORG TABLE AWS_ATTRIBUTE');
Is there a way I can tell Liquibase
Thanks Nathan.
Finally I resolved the problem by using this (instead of the
):
ALTER TABLE AWS_MERCHANT ADD CONSTRAINT PK_AWS_MERCHANT PRIMARY KEY
(MERC_NAME) ;
This problem appears on my setup: DB2 v.8.1 & maven.
I have not tested on DB2 v.9 nor on other database types.
tom ngu
