Hi,
A little clarification. Actually, TBL1.CATEGORY and/or TBL2.CATEGORY may hold a binary value having multiple binary(ies) '1'.
Each binary value column represent an business attribute.
If a binary value column is equal to '1', it means that the business attribute is True,
otherwise it is false.
I adopted this avoid defining a detail table to table TBL1. Idem to TBL2.
If TBL1.CATEGORY | TBL2.CATEGORY > 0
=> it means that we have at least one common business attribute that is TRUE for TBL1 and TBL2.
Regards
W.Alf
On 9/17/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:"Kevin Grittner" <Kevin.Grittner@wicourts.gov > writes:
> On Mon, Sep 17, 2007 at 2:49 AM, in message
> <1190015368.148293.56830@y42g2000hsy.googlegroups.com>, valgog
> < valgog@gmail.com> wrote:=20
>> Are you sure you understood what was the question?
>>
>> Is the TBL1.CATEGORY = TBL2.CATEGORY the same as TBL1.CATEGORY &
>> TBL2.CATEGORY > 0?
> Yes, given that he stipulated that one and only one bit would be set.
Really? In that case, isn't this bit-field just a bad implementation of
an enum-style field?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
