Groups | Search | Server Info | Login | Register
Groups > comp.databases.ingres > #3898
| Newsgroups | comp.databases.ingres |
|---|---|
| Date | 2023-09-12 23:53 -0700 |
| References | <757cd439-a568-4385-ad7e-b1bb6bf12a97n@googlegroups.com> <80ea7a3c-5dab-48ed-bc0d-cd39836ef4ecn@googlegroups.com> |
| Message-ID | <442e0ed1-b216-4d64-b400-3e0b707fc22en@googlegroups.com> (permalink) |
| Subject | Re: Triggers and locks |
| From | Fabrizio Di Renzo <fabrizio.direnzo@bucap.it> |
Thank you all, we will try to use dbevent, I think this is a good idea. We never used it, but it seem the better solution. > ps. your AFTER INSERT rule looks like it needs to refer to the new record rather than the old record? We need to refer to old record Fabrizio
Back to comp.databases.ingres | Previous | Next — Previous in thread | Next in thread | Find similar
Triggers and locks Fabrizio Di Renzo <fabrizio.direnzo@bucap.it> - 2023-09-12 02:40 -0700
Re: Triggers and locks Roy Hann <specially@processed.almost.meat> - 2023-09-12 10:36 +0000
Re: Triggers and locks G Jones <geraint.jones@ndph.ox.ac.uk> - 2023-09-12 07:41 -0700
Re: Triggers and locks Paul White <shift7solutions@gmail.com> - 2023-09-12 22:03 -0700
Re: Triggers and locks Fabrizio Di Renzo <fabrizio.direnzo@bucap.it> - 2023-09-12 23:53 -0700
Re: Triggers and locks Roy Hann <specially@processed.almost.meat> - 2023-09-13 08:54 +0000
csiph-web