On December 2, nickm at go2.ie said:
> [display database error] which won't mean anything to the average
> end user. Or try and parse the error messages from the database and
> report something sensible to the user.
Or three, design your GUI and your database in a sufficiently
consistent fashion that neither one nor two needs to be done. It can
be done. I've worked both on and with such systems. Of course, there's
that word "design". A lot of people don't like that, preferring the
more immediate verb "congeal"[1]
> You're always going to need to do some validation directly in the GUI,
> unless you want a really unusable GUI.
What, like a web-based frontend? :)
Cheers,
Waider.
[1] Attribution: John Bourke, a friend from college. In context,
"This code wasn't written. It /congealed/."
--
waider at waider.ie / Yes, it /is/ very personal of me.
smarry says, "nnnngh, would rather swan dive into a bowl of battery acid with
Kris Kristofferson"
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
