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?
>
> I'm a bit of a purist but I only like getters and setters for the values of
> the form. I don't like to see getValueOnAMonday() etc.
>
> -Original Message-
> From: Murray Collingwood [mailto:[EMAIL PROTECTED]
> Sent: 06 September 2005 00:00
> To: user@s
.
2.
I'm a bit of a purist but I only like getters and setters for the values of
the form. I don't like to see getValueOnAMonday() etc.
-Original Message-
From: Murray Collingwood [mailto:[EMAIL PROTECTED]
Sent: 06 September 2005 00:00
To: user@struts.apache.org
Subject: De
Hi all
Just like to say I really appreciate the help you guys provide us newbies. I'm
looking
forward to the day I will be able to help others...
What convention do people normally use for dealing with NULL values from an SQL
database?
I can retrieve them okay.
I can store them in my form cl
5 matches
Mail list logo
