Is there a reason beside 'performances' to have spaces in some of the operator defined in Criteria ?
I find it a little bit problematic to do a mapping between operators (I'm trying to implement an boolean query page). To explain further the problem. I have a table that does the mapping id <-> criteria operator. I have several tables that represent a list of operators corresponding to a given data type (text, number, date, singlevalue, multivalue). here there is a mapping operator id <-> bundle key the bundle key is used for l10n since I want the list to be displayed in a given locale (for example I want to translate contains, like, etc..., thus the key). When submitting my form I have several criterion made of operator id, field name, value. >From these 'web criterion', I'm building a Criteria object based on the objet we want to look for (I modified MapBuilder to have a mapping field/column) A bit complicated but I'm force to initalize the DB with the same string as the one in Criteria (w/ the spaces) which may sound bizarre :) Also if you know of a simpler way to build boolean queries on an object (we will assume the queries can only be made about the properties of an object and we cannot query for relation between objects..limitation for now, but I don't know right now how to handle this in a simple way without the user typing some type of advanced boolean queries via SQL like language in a text area... -- St�phane Bailliez Software Engineer, Paris - France iMediation - http://www.imediation.com Disclaimer: All the opinions expressed above are mine and not those from my company. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
