Pierre van Rooden wrote: > Update of /var/cvs/src/org/mmbase/util/xml > In directory james.mmbase.org:/tmp/cvs-serv2516/xml > > Modified Files: > BuilderReader.java > Log Message: > Removed the restriction that you can only assign datatypes that are > assignment compatibele. > There is no reason for the restriction, and adding it only ensures that old > objectmodels no longer function. > While having different datatypes for mmabse typesd (i.e. datetime for a LONG) > is peculiar, this is not wrong, as how MMBase stores data in the databse and > how it chooses to validate it are two different things (even though they > ideally match). > I am reversing this change - otherwise old date fields will not work on > MMBase 1.8
I do not agree. I think the problem should have been addressed in the inherit method of DateTimeDataType, and perhaps on the spot where it does value comparisons. I think data must always be restricted to the restrictions of storage, otherwise, er, it cannot be stored, which is quite essential. E.g. if your date is stored as an INTEGER, it _must_ apply a maximal value in 2037, even if that is not explicitely specified, and a value of 2040-01-01 must be _invalid_, because it cannot be stored. Furthermore this change causes test-cases to fail. Michiel -- Michiel Meeuwissen mihxil' Peperbus 107 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
