Subject | Other upgrading difficulties with Firebird |
---|---|
Author | montgomery_list |
Post date | 2002-05-06T05:54:11Z |
Hi,
The fun never stops...
Now that I have restored most of our client's database files, I find
there are some big problems with our database metadata. In many,
many locations we are using newly-reserved keywords for column names,
like "ACTION", which are of course liberally used by stored
procedures and triggers.
What's the best way to rename a column with a reserved word as its
name? How do I even write the script commands without FB choking on
the reserved words?
On the bright side, FB seems faster than v4.2...at least the error
messages seem to come back faster! ;)
Best Regards,
David Montgomery
The fun never stops...
Now that I have restored most of our client's database files, I find
there are some big problems with our database metadata. In many,
many locations we are using newly-reserved keywords for column names,
like "ACTION", which are of course liberally used by stored
procedures and triggers.
What's the best way to rename a column with a reserved word as its
name? How do I even write the script commands without FB choking on
the reserved words?
On the bright side, FB seems faster than v4.2...at least the error
messages seem to come back faster! ;)
Best Regards,
David Montgomery