When you do pop back I'm curious. Are the CreateSQL statements created on the fly or stored? Either way they're dead handy.

Roy Lambert

Don't know for sure Roy, but pretty sure most of the system tables like Tables, TableColumns etc. are generated on the fly.

i.e. they don't really exist as EDB table files anywhere, but data is loaded into EDB-like structures so we can manipulate them as such.

Adam

Roy,

<< When you do pop back I'm curious. Are the CreateSQL statements created on
the fly or stored? Either way they're dead handy. >>

They're generated on-the-fly.  I'm finishing up 2.16, and it has a new SET
INFORMATION COLLATE statement that allows you to set the collation used for
these areas of the information tables (CreateSQL, etc. for columns, index
columns, and procedure/function params).  As you can imagine, this is used
in a new EDB migrator that allows you to migrate databases from one
configuration to another, including migrating across Unicode/ANSI character
sets, encryption passwords/signatures (!!), and any other customizations.

Tim Young
Elevate Software
www.elevatesoft.com

Tim


>They're generated on-the-fly. I'm finishing up 2.16, and it has a new SET
>INFORMATION COLLATE statement that allows you to set the collation used for
>these areas of the information tables (CreateSQL, etc. for columns, index
>columns, and procedure/function params). As you can imagine, this is used
>in a new EDB migrator that allows you to migrate databases from one
>configuration to another, including migrating across Unicode/ANSI character
>sets, encryption passwords/signatures (!!), and any other customizations.

Just typical - I spend ages coding to build that facility in then you go and add it

Hmm I wonder how much code I can take out - I do love a good diet!

Roy

Roy,

<< Just typical - I spend ages coding to build that facility in then you go
and add it >>

Chicken and egg - I tried in the past, but it really couldn't be done until
the ANSI/Unicode switch was added, and that took months to finally get
developed and ironed out.

<< Hmm I wonder how much code I can take out - I do love a good diet! >>

A *lot*.  I migrated a database between ANSI and Unicode, and between
one of your databases (special encryption password) and a non-customized
one.  It's really just a matter of set the parameters and go.

Tim Young
Elevate Software
www.elevatesoft.com

Tim


Rats, now I have 2.16b2 I think misread this. It only applies to migration not to altering things within an existing database. No diet for my code but at least I have things working.

Roy Lambert