Re: [Modeling-users] Primary keys with more than one attribute -- to be supported ???

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

        Hi,

Ezra E. <sf-...@pr...> wrote:
>    Reading section 2.3.2.1 of the documentation (nice docs, by the way!) I
> see that support has not yet been added for multi-attribute primary keys.
> Is there an intention to add that?  If so is there a time frame?

There is no ETA for this feature, but there is an intention to add that,
yes, the first time someone really needs it ;)

  Apart from some quick-and-dirty code that probably slipped through my
  fingers and gained access to the cvs main trunk, the framework
  normally does not assume that an entity has only one PK attribute.
  Since you suggest that you're an experienced EOF-user here are some
  more details: the implementation of such a feature implies:

    - creating the delegate interface for the DBContext which in turn
      would implement databaseContextNewPrimaryKey().

    - have DBContext.prepareForSaveWithCoordinator() ask the delegate
      for a value before the AdaptorChannel gets a chance to provide its own
      primaryKeysForNewRowsWithEntity()

NB: The delegation code is already ready to be used, even if not used yet
http://modeling.sf.net/API/Modeling-API/public/Modeling.delegation-module.h=
tml

  Last, we'll need to test that relationships from/to entities w/
  compound pks behave as expected.

Please fill in a RFE if you feel like you need this: this public list of
requests is the best mean to prevent me from forgetting about users'
requests!

-- S=E9bastien.