Re: DB Data Object Feature Request
Alan Knowles <alan <at> akbkhome.com>
2006-05-01 02:23:25 GMT
Please make sure you file a bug (or add it to an existing report) - then
keep bugging me to look at it.
Torsten Roehr wrote:
>>""Justin Patrin"" <papercrane <at> gmail.com> schrieb im Newsbeitrag
>>news:432beae0604281319x2015063fo830987a35cb5eb76 <at> mail.gmail.com...
>>On 4/28/06, Matt Friedman <matt.friedman <at> gmail.com> wrote:
>>>We have a situation where we have modelled Messages. In our system a
>>>Message can be sent out in one or more Languages. The intrinsic
>>>meaning of the Message is the same regardless of the Language.
>>>Therefore, each Message has a dual part PK (MessageID, LanguageID).
>>>Thus, Messages with the same meaning have the same integer PK field
>>>and the second part of the PK differentiates each message based on
>>>Language. This is the correct modelling of the PK for this subject
>>Also, as a quick fix for this problem while multi-column PK support is
>>added to DB_DO (who knows when it will actually be done) you can just
>>add a new column to this table, ID, which has its own sequence. That
>>way you also have a 1 column PK, which makes it work with DB_DO, and
>>also have your other data. (note: having your PK be ID would not stop
>>you from still having a UNIQUE constraint or an INDEX on MessageID,