Re: Creating Not Null contraints in SE
- From: JaxenT <jaxent@xxxxxxxxx>
- Date: Fri, 22 Jun 2007 20:13:18 -0000
Oh if I could ... But dbexport needs to use dbschema to work and
dbschema is failing with -100 errors. The alter table worked but that
did not fix the 100 errors. I am just building a huge brute force sql
file to run instead of trying to be smart and doing a program to
rebuild it all. I've gone through 50 of 180 tables and 38 so far have
to be rebuilt. I have four other dbs of about the same size to do as
well, I bet the problems there will be about the same. It is mind
nulling. Thanks for all your help though.
NOT NULL constraints cannot be 'ADDED' they have to be MODIFIED:
ALTER TABLE xredit_cards MODIFY (somecolumn some type NOT NULL
CONSTRAINT some_constr_name);
But, why struggle. When you dbexport, have dbexport write the SQL
file to disk and just edit the disk file to change the constraint
names in the CREATE TABLE statements in the file. Alternatively, for
others reading htis who are not using SE - sonce we've already
determined that myschema no longer works for SE databases (sigh) - you
can use the '-l' option to myschema to create a dbimport compatible
schema with the constraints renamed for you (actually for NOT NULL
constraints I just drop the constraint names so that the new database
creates new names.
Art S. Kagel
.
- References:
- Creating Not Null contraints in SE
- From: JaxenT
- Re: Creating Not Null contraints in SE
- From: Art S. Kagel
- Creating Not Null contraints in SE
- Prev by Date: Re: Workgroup Edition with HDR
- Next by Date: Re: Informix beats Oracle
- Previous by thread: Re: Creating Not Null contraints in SE
- Next by thread: ODBC Error
- Index(es):
Relevant Pages
|
