cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weddle, Anthony" <>
Subject Validation
Date Mon, 13 Apr 2009 23:26:50 GMT
The documentation talks of removing validation as a concern of the GUI,
by using object validation that gets done before any commits. However,
validation can continue to be needed in the GUI since it is always nicer
to let users know of problems early on (such as the maximum length of a
value, that a value must be a number or a value must not be null, as
well as business validation). Is there some way to have database
constraints visible to the GUI developer, perhaps through use of the
class generation templates (by adding constraints as constants in the
superclass, for example)?




NOTICE - This message and any attached files may contain information that is confidential,
legally privileged or proprietary.  It is intended only for use by the intended recipient.
If you are not the intended recipient or the person responsible for delivering the message
to the intended recipient, be advised that you have received this message in error. Any dissemination,
copying, use or re-transmission of this message or attachment, or the disclosure of any information
therein, is strictly forbidden. BlueScope Steel Limited does not represent or guarantee that
this message or attachment is free of errors, virus or interference. 
If you have received this message in error please notify the sender immediately and delete
the message.  Any views expressed in this email are not necessarily the views of BlueScope
Steel Limited.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message