Hi, > > Doesn't look like DBIx::Recordset supports composite primary keys - is > that by design or it just a feature you haven't needed? >
I didn't need it so far. A long time ago somebody submitted a patch to me that builds compsoite prim key support into DBIx::Recordset, but it had such a high impact on performance that I didn't included it. > Where it would be most useful for me is on Execute updates, since that's > how you're distinguishing keys from values - I guess you can use an > explicit where clause but it's much less clean than being able to say > '!PrimKey' => 'uid,name', for example. > This makes sense > The change just for updates is fairly modest (patch attached, against > 0.24); changing it across the board looks much less so. > It's maybe better to move to split into SetupObject, so you don't have to do it on every update. The other thing is, that other methods (e.g. Search)won't work anymore correct with that composite prim key (at least they behave different), because they don't expect a comma separated value. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
