Whether you store nulls in your database is really a design decision you
should be making based on your requirements.
Taking the date example for a moment. If the date is required then it
shouldn't be able to be null in the database and a record shouldn't be
created until you have a valid dat
If the value of "endDate" is null the page fails with an error message from
> beanutils.
I think if the endDate is null, the would silently put empty
string as the value. Wondering if the exceptions you are seeing are causing
by something else. What is the exception by the way?
Thanks for the suggestion Mark but I'm still not quite sure how you work this.
Considering an end date for a product how would you code the input text box on
the
editProduct JSP form?
Normally:
If the value of "endDate" is null the page fails with an error message from
beanutils.
If we
I would do number 3
Look at
A few comments on the others.
IF a database value is NULL keep it that way. A NULL is a permissible value,
and you should not attempt to correct it, with empty strings etc.
Consider an end date for a product. You may never have one, and a NULL is a
good value here.
4 matches
Mail list logo
