Ed Leafe wrote: > On Dec 25, 2006, at 2:19 PM, Paul McNett wrote: > >> I'm keeping two dicts keyed on PK: _mementos and _newRecords. The >> _newRecords dict contains no useful values (the PK's presence in the >> dict tells us that it is a new record). > > Just a quick question: will this work with tables with compound PKs? > What about tables with no PKs?
when I was splunking around the data layer I was thinking the PK support wasn't quite right, but never looked into it fully. To me, a PK should be an expression. the expression can be a field, or a set of fields, but should be able to be any expression. Therefor, if you are storing PK values client side, it is just one value, regardless of how it is stored in the db. Not that anything other than a single field is a good idea, but if you want to support anything, you may as well support anything, and I bet the expression way is better than trying to keep track of what fields are used. No clue how this would work with the "auto generated temporary keys" that dabo uses to keep new P/C/G data organized client side before it gets committed. I have yet to see anything I really liked other than application generated GUIDs. (not saying I don't like how dabo does it, cuz I didn't try to figure it out.) Carl K _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
