Dabo Trac wrote: > #1175: Enhance dCursorMixin to support (1) editable and (2) compound primary > keys > --------------------------+------------------------------------------------- > Reporter: aecker | Owner: somebody > Type: enhancement | Status: closed > Priority: major | Milestone: 0.8.3 > Component: db | Version: 0.8.4 > Resolution: invalid | Keywords: editable multiple compound pk > --------------------------+------------------------------------------------- > Changes (by ed): > > * status: new => closed > * resolution: => invalid > > Comment: > > Compund PKs are supported in Dabo. The docstring of KeyField in dBizobj > reads: "Name of field that is the PK. If multiple fields make up the key, > separate the fields with commas". > > What is *not* supported, and never will be, are modifiable PK values. This > makes no sense at all, since there is no way to tie a record in a > recordset with its source in the database. > > I would strongly recommend an internal, hidden PK for database usage, > along with a visible, editable candidate key for the benefit of the human > beings who interact with this data. >
If i'm in the need of a candidate key for the benefit of humans, i just add a unique key field to the record. Let the user put into this whatever he wants. Key fields for relational connections (pk, fk) should always be pure technical keys (at least, that's my understanding). I never needed compound primary keys except for very rare situations, mostly because i was forced to use existing schemas. The effort for using compound primary keys always turned into a lot of extra work. Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
