There are various other problems that needs to be
taken care off. One of the annoying things is that for instance they store a timestamp in
mysql in a special format. It > looks like this:
For the wl_notificationtimestamp there is then code
that either wants to place a 0 in it,
or check that there is a 0 in it, or some other weird thing. There are probably various
other things like this.
At some point of time I traversed whole code and checked for timestamp usages.
All of those were replaced with $db->timestamp(), which chooses correct timestamp.
If some patches were commited later in, I could miss the review.
I really dislike the NOT NULL constraints with a
default value on such fields.
I would either like to drop the default, drop the NOT NULL constraint (and default),
or change the schema in such a way that they are not needed. In case of the watchlist
this
should be rather easy. We could just drop the default and delete
the record instead of setting it to some state that doesn't make sense.
Well, this is maybe wrong thing done, but using NULL's might need reviewing code again
:)
Domas