Interesting. I've only ever used and seen qualifiers used on some type of text discriminator column. I don't know why it never occurred to me to try a boolean.
-- Kevin On Thu, Feb 19, 2009 at 3:15 AM, Andrey Razumovsky <[email protected]> wrote: > Hi Michael! > > I don't need a query. I need entity qualifier. In CM this only can be mapped > with a string. Currently I solved the problem by manually setting qualifier > in code. I think this is a limitation, and I'll open a JIRA if my suspicions > will confirm. > > 2009/2/18 Michael Gentry <[email protected]> > >> Well, you can create a query in CM with the magnifying glass icon (or >> Project -> Create Query menu) and specify it there. You might need to >> use the underlying data value. For example, I had an isFilled Boolean >> attribute mapped to an integer database type and in my query I >> specified "isFilled = 0". I don't think I ever tried "isFilled = >> false", but I might have to give that one a shot now that you've made >> me curious. >> >> /dev/mrg >> >> >> On Wed, Feb 18, 2009 at 10:14 AM, Andrey Razumovsky >> <[email protected]> wrote: >> > Hello, >> > >> > Can I specify qualifier via string (in Modeler), which checks boolean >> > attribute, e.g. something like "abort=false" or "!abort" ? >> > >> >
