sorry this took so long to respond -- been too busy on the business side of work, little time for code.
On May 18, 2007, at 2:21 PM, John Siracusa wrote: > I think it's pretty clear given that the table definition is right > above it, and contains: > > UNIQUE(product_id, region) ok. that makes some sense. > Which docs? The tutorial of the Metadata docs? The tutorial > obviously can't explain every method. The Metadata docs do explain > what the unique_key method does. > >> the use_key functionality is a bit confusing too -- "Use the unique >> key named KEY to load the object" ... but unique keys don't have >> names > > Really? :) > > http://search.cpan.org/dist/Rose-DB-Object/lib/Rose/DB/Object/ > Metadata/UniqueKey.pm#name now i'm even more confused. maybe at some point in time, the unique_key syntax can mirror the relationships/foreign key syntax -- it wouldn't be backwards compatible ( though maybe it could be coded as such ? ) the rose approach to fkeys & relations is very clear and concise... you choose a class/type, list the field mappings. with unique keys, its still very hard to understand. thats a real hunt through the docs to figure out all of these capabilities. add_unique_keys seems weird too... by the name alone, one would expect add_unique_key( $uk ); add_unique_keys( $uk1, $uk2 ); suffice to say, the unique key implementation/documentation is my least favorite aspect of my most favorite perl module. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
