> Use non-reserved keywords as object names in a dialect 1 database

On Tue, Nov 15, 2011 at 8:43 AM, Thomas Steinmaurer <ts@...>wrote:

> **
>
>
> > Running Firebird 1.5, classic, dialect 1 on Windows and trying to
> > create a trigger like this:
> >
> > CREATE TRIGGER EXTENDED_TEXT_DEL FOR EXTENDED_TEXT
> > ACTIVE BEFORE DELETE
> > POSITION 10
> > AS
> > begin
> > insert into audit_trail
> > (Table_Id,"Action",Primary_Key,data)
> > values (45, 1,
> > old.Extended_Text_Type||"|"||
> > old.Foreign_Id||"|"||
> > old.Extended_Text_Sequence_No,
> > old.Extended_Text_Type||"|"||
> > old.Foreign_Id||"|"||
> > old.Extended_Text_Sequence_No||"|"||
> > old.Free_Text
> > );
> > END
> >
> > which will give the following error:
> >
> > Dynamic SQL Error
> > SQL error code = -817
> > Metadata update statement is not allowed by the current database SQL
> dialect 1.
> >
> > Note the double quotes around the field name Action.
> >
> > Any idea how I can run this statement?
>
> You can't with dialect 1. Delimited identifiers are supported by dialect
> 3. Use non-reserved keywords as object names in a dialect 1 database.
>
> --
> With regards,
> Thomas Steinmaurer
>
> * Upscene Productions - Database Tools for Developers
> http://www.upscene.com/
>
> * My Blog
> http://blog.upscene.com/thomas/index.php
>
> * Firebird Foundation Committee Member
> http://www.firebirdsql.org/en/firebird-foundation/
>
>
>


[Non-text portions of this message have been removed]