> -----Oorspronkelijk bericht----- > Van: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Namens Pierre van Rooden > Verzonden: maandag 20 december 2004 19:07 > Aan: MMBase Developers > Onderwerp: [Developers] VOTE: HACK: Changing > FieldValueBetweenConstraint > > > FieldValueBetweenConstraint is a Query constraint that is used to > compare a field with two values.
Can you explain about this please? How dous a field have multiple values? or are these values generated by functions on the field? Ernst > Currently, these values are always converted to strings, no > matter what > the actual type of the value is. > This causes some serious problems if you want to use dates. I frimly > believe catsing valeus to string is not something that should > happen in > the Constraint object, but in the query handler > Especially dates, whose format may differ according to the > database or > storage device. > > As such, I wish to propose to change > FieldValueBetweenConstraint so the > getUpperLimit() / get Lowerlimit() methods return the actual > object, and > not a String. Changes needed for this change in the interface are, as > far as I can tell, only required in core classes. > > Included are the files you need to replace: > > bridge/util/Queries.java > storage/search/FieldValueBetweenConstraint.java > storage/search/implementation/BasicFieldValueBetweenConstraint.java > storage/search/implementation/BasicSearchQuery.java > > This hack is part of the FieldTypes project and intended for > MMBase 1.8 > > START OF VOTING: 2004-12-20 18:00 > END OF CALL: 2004-12-23 18:00 > > [_] +1 (YES) > [_] +0 (ABSTAIN ) > [_] -1 (NO), because : > [_] VETO, because: > > > -- > Pierre van Rooden > Mediapark, C 107 tel. +31 (0)35 6772815 > "Some Drink at the Fountain of Knowledge. Others Just Gurgle." > _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
