At 11:12 AM 3/30/2001 +1000, Geoff Worboys wrote:

>And if I ever need to move to a different platform there is a
>good chance that gbak will not have problems with the backup database
>(since it does not have all the confusing constraints installed) and
>so I can move the backup database using gbak and then restore on the
>new platform.

I would suggest that you store all your data as text if you want
to make it portable. Integer and floating point types introduce
alignment and 'endian' issues.

>One of the reasons for using gbak is to reset version numbers on the
>metadata. Will the application of alter table commands to add
>computed fields, constraints etc impact this? That is; do I get a
>version number increment for each and every computed field and
>constaint added - perhaps I can minimise this by attempting to add all
>such changes in a single alter table command.

The version number goes up on the commit, not on the statement. I
believe that the method I suggested will leave versions set at two or
possibly three for tables with triggers.


Regards,

Ann
www.ibphoenix.com
We have answers.