Hi again,
We used default values; the Don’t ignore NOT NULL option was checked. This occurred multiple times, with different databases. I was using the SQL Server specific migration.
I understand about the defaults incompatibility issue. We use simple defaults, so I’m sure we’re getting the full brunt of the problem, thankfully, and the scripts worked fine.
BTW, pgAdmin has been a fantastically helpful tool.
Cheers,
Roger
-----Original Message-----
From: Dave Page [mailto:dpage@vale-housing.co.uk]
Sent: 20 May 2003 10:33
To: Roger Gordon; pgadmin-support@postgresql.org
Subject: RE: [pgadmin-support] Miigration Wizard ignores not nulls & default values
-----Original Message-----
From: Roger Gordon [mailto:Roger@emojo.com]
Sent: 19 May 2003 10:46
To: pgadmin-support@postgresql.org
Subject: [pgadmin-support] Miigration Wizard ignores not nulls & default values
Hi,
Noticed 2 problems migrating from SQLServer 2000 using pgAdmin 1.4.12:
1.NOT NULLs other than the primary key code migrate over as NULLs
2.Default values are not migrated
I’m writing a script to fix these errors, but any advice would be most appreciated….
Hi Roger,
Did you have the 'Don't ignore NOT NULL' option checked when you migrated?
The default values are not migrated at all as you say (though they were years ago). Primarily this is because they tend to cause too many problems with syntax incompatibilities between DBMSs.
Regards, Dave.
