Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.postgresql > #412
| From | "M. Strobel" <sorry_no_mail_here@nowhere.dee> |
|---|---|
| Newsgroups | comp.databases.postgresql |
| Subject | Re: perl trigger question |
| Date | 2012-09-26 10:05 +0200 |
| Message-ID | <acfr9hFdt67U1@mid.uni-berlin.de> (permalink) |
| References | <k2t228$e33$1@dont-email.me> |
Am 13.09.2012 18:36, schrieb Marky Mark: > Hi, > > the psql docs say that a perl trigger can return one of the following: > > return; > Execute the statement > "SKIP" > Don't execute the statement > "MODIFY" > Indicates that the NEW row was modified by the trigger function > > Skipping, silently ignoring a (failed) INSERT is not nice for my purposes, I'd like > to get at least some error message so the user would know something went wrong. > > Can I not do this or am I dyslexic? How about elog? /Str.
Back to comp.databases.postgresql | Previous | Next — Previous in thread | Find similar | Unroll thread
perl trigger question Marky Mark <marky@mark.com> - 2012-09-13 18:36 +0200 Re: perl trigger question "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-09-26 10:05 +0200
csiph-web