Re: SQL (not embedded)

Has anyone else had this issue (we are on release 7.1):

I have a SQL script with a CREATE TABLE statement in it. There are two
columns in the table (among others), both are DATE types, and one is right
after the other.

I want to assign default values to both of these dates, so after the
CREATE TABLE statement, I use two ALTER TABLE commands to set the default
value.

When the two ALTER TABLE statements are one right after the other in the
script, only the first one takes effect; the other one runs, but does not
set the default value, nor is there an error on the SQL report. If I
separate the ALTER TABLE statements by moving one to the end of the ALTER
TABLE section in the SQL script, both work fine, and both date fields have
their default value set. I know the syntax of both is correct, since when
they are not contiguous, they both execute as desired.

Any ideas?

Thank you,

Doug



--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.