John Cohorn wrote:
It seems to me that all information about acceptable values, constraints
and
types for columns is already present within the table definitions so
duplicating those checks and definitions within the application and user
view is folly.
Well, there I'd disagree with you. With a web-based application you
might typically have three levels of validation:
1. Javascript on the client side
2. Server-side validation
3. Database validation
The view of data at the application level might well be different from
that at the database level (if you insert data via a view or function
for example). Providing test/erros that mean something to the
application (and its users) is something that your application needs to
handle. Hopefully your application framework provides some help with
these tests.
But, you still want to extract the column-names etc. and I'm afraid that
will require parsing the error messages at present. There has been
discussion on returning more structured information in the error
packets, but that will mean a change in the communication protocol, so
won't ever apply to older versions of the database.
HTH
--
Richard Huxton
Archonet Ltd
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
