Hello.
Today, while testing user validation (for future LDAP data backend) an error
message from JDBC popped up on me a few times. Sybase, which I am using does
not permit updates on timestamps column. I've already changed that in the schema.
I looked a bit through the sources, and I've come to the conclusion that we really
don't want thte MODIFIED column to behave like a timestamp (mysql style), but as
ordinary (non-magical) date/time field. It was discussed on the list some time
ago (see http://www.mail-archive.com/[email protected]/msg04041.html
and followups). I tend to think that setting MODIFIED=NOW in setPerm is a bad
idea, because there are things that change in the perm hasthable we wouldn't
like to consider a modification of the user data - notably the access counter.
We probably should have a method setModifiedNow() method that the application
will call right after changing some perm value that is considered important.
Comments?
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
