Re: [Modeling-users] primary key + class property

[Sebastien B. <sbi...@us...>]

Yannick Gingras <yan...@sa...> writes:
> On Thursday 20 February 2003 02:49 pm, Yannick Gingras wrote:
> > I saw in the FAQ that I could see my primary keys by setting them as
> > class properties.  If I try this, I need to set them by hand.
> >
> > How can I have *automatic* primary keys that I can see ?
>=20
> By setting default value to 0 + isRequired to 1.

Could you please be more specific? Do you say that automatic generation
of primary key does not work if you define it as a class property???
More on this: the framework does not support setting the primary key of
an object by hand --that's why I really want more details on what
happened to you here.

  If this is the case, this is a bug I really want to trace: this should
  NOT happen, and I cant even see now how automatic pk generation could
  be defeated when the primary key is a class property (it is nnot even
  checked when insertedObjects of an EditingContext are processed).

However you are right: the default value should be 0, and isRequired
must always be set to 1 for a PK (being a class property or not).


-- S=E9bastien.