hi,
If information in your dbms is ever modified by anything other than entity beans then
enforcement of referential integrity via triggers, stored procedures or declaratively
when creating tables is the only safe way to go.
For tables that are only updated through eb's I place the validation within the eb, is
much easier to implement and the application will be more portable.
>>> Adena Galinsky <[EMAIL PROTECTED]> 29/08/00 09:42:23 >>>
I've heard that data validation should take place in the entity bean (to
centralize the logic), or a dependent object (to centralize the logic while
also allowing it to execute on the client).
Should there also be data validation in the stored procedures in the
database? On the one hand it seems redundant, but on the other hand it
seems the only safe way to go.
-Adena
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
This email or attachment(s) may contain confidential or legally privileged information
intended for the sole use of the addressee(s). Any use, redistribution, disclosure, or
reproduction of this message, except as intended, is prohibited. If you received this
email in error, please notify the sender and remove all copies of the message,
including any attachments. Any views or opinions expressed in this email (unless
otherwise stated) may not represent those of Canterbury Health Ltd.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
