On Wednesday 19 November 2008 08:31:14 am 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.
Learn something new everyday. Would you explain how the compound key works for the benefit of others (maybe I'm the only one that does not know). Where/how does the PK get updated on a new()? Can the compound PK be of any data types? So if I wanted Invoice# and Location as my PK and Invoice# = int and Location = str can I mix the two? -- John Fabiani _______________________________________________ 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]
