Really thanks for your support.
Derby doc doesn't say much about this, but it seems that I have to specify
default="CURRENT_TIMESTAMP" to make them filled.
In fact the behavior is good, by not adding "default" clause, and adding
required = "false", I expect my DB to init it to NULL or equivalent.
Shinkan wrote:
Maybe that is because my schema doesn't NULL the value correctly ? Here is
the column definition :
And the generated SQL:
expiration TIMESTAMP,
That looks ok to me. Based on this definition
criteria.add(TestPeer.EXPIRES, (Object) null, Criteria.ISNULL)
seems to be the right
Hi !
Nope, I tried it before, but it seems that "IS NULL" is different from "=
{ts '00-00}".
By the way, the deprecated new Date(0, 0, 0, 0, 0, 0) corresponds to "{ts
'1899-12-31 00:00:00.0'}" on my env.
I could also build a custome crit like dateCrit.add(TestPeer.EXPIRES,
(Object)"={ts '-
Hi,
criteria.add(TestPeer.EXPIRES, (Object) null, Criteria.ISNULL)
doesn't work?
Regards,
Shinkan wrote:
Hi again there !
I have a TIMESTAMP type column in a schema, and the Torque maps it to
java.util.Date, which is really convenient most of the time.
BUT, I would like to check for this col
Hi again there !
I have a TIMESTAMP type column in a schema, and the Torque maps it to
java.util.Date, which is really convenient most of the time.
BUT, I would like to check for this column nullity, SQL point-of-view.
That's to say, I have to check that this field, let's call it "expires", is
NUL
