Re: Must class qualifier be an entire field?

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Tue Feb 27 2007 - 09:39:00 EST

  • Next message: Andrus Adamchik: "Re: security - revisited"

    This works. But of course it is up to the programmer to ensure that
    the qualifier is built in such a way that multiple subclasses do not
    overlap.

    Andrus

    On Feb 27, 2007, at 4:24 PM, Mike Kienenberger wrote:

    > I've not used single-table inheritance, but I'm pretty sure the
    > qualifier is just a qualifier and completely independent of columns.
    >
    > It could be "0 = mod(random(), 2)" if the database supported the
    > functions.
    >
    > In this case, the fastest thing to do is to just test your
    > alternate qualifier.
    >
    > On 2/27/07, Török Péter <torok..llround.net> wrote:
    >>
    >>
    >> Hello,
    >> is it necessary to have a full column reserved for the class
    >> qualifier in
    >> case of single table inheritance?
    >> I.e. instead of qualifier
    >> personType = 'CUSTOMER'
    >> would something like
    >>
    >> personType like 'C%'
    >> work? Anyone tried such a thing yet?
    >> Thanx in advance,
    >> Péter
    >>
    >

    This archive was generated by hypermail 2.0.0 : Tue Feb 27 2007 - 09:39:28 EST