Subject Database Objects Will Work Even With Invalid Dialect 3 Syntax - how to tell
Author Nick Upson
If I set a 1.5.2 database to dialect 3 using gfix and then do a
backup/restore successfully is that sufficient to prove that I don't have
any invalid triggers, SP, etc as described below?


http://www.ibphoenix.com/main.nfs?a=ibphoenix&l=;PAGES;NAME='ibp_60_dialect'

Database Objects Will Work Even With Invalid Dialect 3 Syntax
Another thing I discovered is that certain database objects (I've tried this
with triggers and stored procedures) will continue to work in dialect 3 even
though they are using functionality of dialect 1. Here is an example trigger
that clearly shouldn't work in dialect 3:

create trigger blah_trigger for blah
before insert
as
begin
new.v1="blah";
end!!
This trigger is valid in dialect 1. The double quotes are allowed for string
literals. However, you will get an error if you try to create this trigger in
a dialect 3 database. You will get the "Column unknown" error. But, this is
where it gets interesting...

If this trigger was created in a dialect 1 database and migrated to a dialect
3 database (changing the database dialect via gfix), the trigger will
continue to work. Why you ask...


--
Nick
-----We Solve your Computer Problems---
Founder & Listowner of the Prolifics User Group
Panther, Ingres, UNIX, Interbase, Firebird - Available Shortly