On Sat, 2002-09-28 at 00:17, Gavin King wrote:
> Yes, well you see that was my understanding also. My reading of that
> statement is that the identity column *on its own* is a unique key of the
> table (whether theres a UNIQUE constraint or not).
>
> So a primary key constraint that includes an id
> IDENTITY fields in MS SQL (and Sybase, for that matter) are very simple:
> there can be only one IDENTITY field per table, and every INSERT is
> guaranteed to generate a unique value for that field.
Yes, well you see that was my understanding also. My reading of that
statement is that the ident
On Fri, 2002-09-27 at 19:15, Gavin King wrote:
> Thats what happens when you write emails at 3 am. I meant to express my
> interest in the fact that MS SQL can generate values that are unique, not
> for the whole table, but only for other rows with the same values in the
> other primary key fields.
On Fri, 2002-09-27 at 11:37, Gavin King wrote:
> Damn! thats a tough one. I'm almost tempted to say that the best solution
> would be to implement the new cirrus.hibernate.persister.ClassPersister
> interface (in v1.1.1). This would be a decent solution if you just have a
> couple of tables like th
riginal Message -
From: "Chris Winters" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, September 28, 2002 1:38 AM
Subject: [Hibernate] generated field as part of composite key
> I just recently discovered Hibernate and have been extremely pleased
> wi
I just recently discovered Hibernate and have been extremely pleased
with it so far. It will probably be replacing our Entity Beans scheme
shortly.
We're fitting Hibernate to an existing schema which is a little unusual:
every table in the system uses a composite key. I've created a composite
key
