I love the flexibility ibwebadmin is giving me - but I've got one frustrating issue. I make use of before-insert triggers and generators to provide auto-increment fields for primary keys. The problem is ibwebadmin performs value checks on the non-null fields before sending the insert request to database. This means I can't take advantage of my before-insert/update triggers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
try entering an integer value into the primary key field, the value will be overwritten by your trigger. This is not so elegant but it is working for me.
Lutz
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I love the flexibility ibwebadmin is giving me - but I've got one frustrating issue. I make use of before-insert triggers and generators to provide auto-increment fields for primary keys. The problem is ibwebadmin performs value checks on the non-null fields before sending the insert request to database. This means I can't take advantage of my before-insert/update triggers.
Hi Daniel,
try entering an integer value into the primary key field, the value will be overwritten by your trigger. This is not so elegant but it is working for me.
Lutz
I just set the field to '0' and make sure that the trigger populates it with a value if it is zero ( or NULL ).
It will be nice when later versions of Firebird return the value so you can use it.