Re: [Modeling-users] using Modeling w/o primary keys

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

        Hi Duncan,

  Fine, it seems this could make it for that appication(s) you were
  talking about. We'll probably get more info& questions soon ;)

In the meantime let's answer your question, you asked:
> I don't know if any of the client tables have multiple columns that define
> PKs, however, I just did a search on the mail list and saw this:
> http://sourceforge.net/mailarchive/message.php?msg_id=3D6801413
> Has there been any move to support multi-column PKs since then?

We've not moved an inch since then; as I usually say, I now do not have
the time to develop things if this is not at least a user's request,
just because I think features needs to get real-life testing to become
quickly mature and robust. And even then (when people need the feature)
it can sometimes take quite some time to implement --optimistic locking
is a good example.

  So, again, if you have the need for the feature and at least a "test"
  application ("test": from the framework's point of view :) then tell
  us and we'll probably make a step forward!!

Now, to be completely honest, having "raw" support for compound PK
should not be a real problem, however for now I cannot foresee how much
we could get in trouble wrt relationships based on compound PKs. But
since you said that your own needs by now won't use relationships, then
you can be optimistic if this is a feature you definitely need!

-- S=E9bastien.