| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Brian E Gallew <geek+(at)cmu(dot)edu> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: [HACKERS] psql and libpq fixes |
| Date: | 2000-02-10 16:06:22 |
| Message-ID: | 200002101606.LAA05833@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Urhm, wouldn't a better idea be to have something like Ingres' "ON
> ERROR" and "ON WARNING" settings? In Ingres esqlc, you can create
> functions and then tell Ingres to execute them in the even of a
> warning or error. Also, you can say "ON ERROR CONTINUE" and errors
> will then be returned to the application as a status, but otherwise
> ignored.
>
Yes, seems like those are the accepted words to use.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-02-10 16:08:14 | Re: [HACKERS] createdb default arguments |
| Previous Message | Brian E Gallew | 2000-02-10 16:02:32 | Re: [HACKERS] psql and libpq fixes |