| From: | " Víctor R(dot) Ruiz" <rvr(at)infoastro(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Handling error messages |
| Date: | 2001-04-17 16:52:34 |
| Message-ID: | 9bhp01$17bj$1@news.tht.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi:
One of the most obvious things that should do a database is to check
for data integrity and values, but programming with PHP and other
languages I see that we duplicate this task: one on the client side
(with javascript), sometimes on server side (on PHP) and finally
on the database server.
I think the server-side check could be made more easily if the database
server could return error messages in a way we can handle them. For
example, giving an error id (also helpful to translate) and the column and
row affected.
Could be this implemented on Postgres?
--
Víctor R. Ruiz
rvr(at)idecnet(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-04-17 16:56:11 | Re: AW: AW: timeout on lock feature |
| Previous Message | Peter Eisentraut | 2001-04-17 16:48:18 | Real/effective user |