Subject | Re: [firebird-support] Triggers on system tables |
---|---|
Author | Jonathan Neve |
Post date | 2004-12-09T13:11:19Z |
Daniel Rail wrote:
Pity, it could have been useful in my situation, as I wanted to have a
table in my DB with the list of fields for each table (for replication
purposes). Of course, I can use RDB$RELATION_FIELDS for that directly,
but I need to add extra information for each field (mainly, I need to be
able to know whether certain fields should be excluded/included from the
replication). The purpose of my trigger was to populate my table with
the correct list of fields automatically.
Anyway, I'm sure I'll find a workaround, but it's a pity it doesn't work :-)
Thanks,
Jonathan Neve.
[Non-text portions of this message have been removed]
>Hi,Oh really, I didn't know that...
>
>At December 9, 2004, 06:27, Jonathan Neve wrote:
>
>
>
>>Just out of curiosity, I tried putting a trigger on RDB$RELATION_FIELDS,
>>and then I tried adding a field to a table, but I got my DB connection
>>cut... I take it this sort of thing isn't supported?
>>
>>
>
>Even if it would be supported. You would loose your changes the next
>time that you would backup and restore, since the system objects are
>regenerated everytime.
>
>
Pity, it could have been useful in my situation, as I wanted to have a
table in my DB with the list of fields for each table (for replication
purposes). Of course, I can use RDB$RELATION_FIELDS for that directly,
but I need to add extra information for each field (mainly, I need to be
able to know whether certain fields should be excluded/included from the
replication). The purpose of my trigger was to populate my table with
the correct list of fields automatically.
Anyway, I'm sure I'll find a workaround, but it's a pity it doesn't work :-)
Thanks,
Jonathan Neve.
[Non-text portions of this message have been removed]