Sorry for the delayed response. I think what you're proposing is
certainly reasonable. There is no reason that a discriminator column
needs to be a char type, conceptually.
-- KevinOn Thu, Feb 19, 2009 at 8:36 AM, Andrey Razumovsky <razumovsky.andre..mail.com> wrote: > I'd prefer to see some improvements regarding expressions, like this issue > or CAY-1105. What do you think? > > 2009/2/19 Kevin Menard <nirvdru..mail.com> > >> 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 >> <razumovsky.andre..mail.com> 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 <mgentr..asslight.net> >> > >> >> 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 >> >> <razumovsky.andre..mail.com> wrote: >> >> > Hello, >> >> > >> >> > Can I specify qualifier via string (in Modeler), which checks boolean >> >> > attribute, e.g. something like "abort=false" or "!abort" ? >> >> > >> >> >> > >> >
This archive was generated by hypermail 2.0.0 : Thu Mar 05 2009 - 20:37:56 EST