omar <omar2@omnicode.com> writes:
> I'm curious what people think about the following statement considering the
> database typing talk being brought up here. My experience is that more times
> than not I have to put data validation in my client code even when it's
> available on the server, if for no other reason that users don't understand
> what foreign key violation, etc messages mean. It begs the question of
> whether it's really necessary on the server or not. SQLite seems to take the
> position that it isn't since there is no referential integrity and the
> following. To be honest, there's a lot of power in the ability to view
> everything as a string, with of course proper data validation.
I believe that data validation is essential at the server side. The ideal
situation to me is something like data validation on server, errors /
exceptions being risen and then catched by the client code that will translate
them to a suitable message.
Inserting data validation on client side helps with simple input and eliminate
the average number of roundtrips needed for getting the data stored, but
shouldn't be the only validation done.
--
Jorge Godoy <jgodoy@gmail.com>