I was wondering if the limit on one primary key field only was coming
out of the "encouraging of clean design" or was just a technical limitation.
I have some classes in my "legacy" app that are uniquely identified by
two or more attributes, and I was just catching db layer exception when
the
On 10/12/07, Simone Cittadini <[EMAIL PROTECTED]> wrote:
>
> I was wondering if the limit on one primary key field only was coming
> out of the "encouraging of clean design" or was just a technical limitation.
Search the archives - this has been discussed many times. There is
also a FAQ entry tha
2 matches
Mail list logo