Hi! Quote SQLObject does not support primary keys made up of multiple columns (that probably won't change). It does not generally support tables with primary keys with business meaning -- i.e., primary keys are assumed to be immutable (that won't change). /Quote
Many relational DB-Designs come with multiple columns forming the Primary Key of a Table. (so did mine) We have also many (very performant) views which do not have unique keys and return the data the way we want them to to this. I think it would be not very productive to reconstruct these views in SQLobject. So far I have used the following to create unique integer id (works for numeric values only) simplified (the PK's must be lpadded with '0' to the maxmum length of the PK) select pk1||pk2||pk3 as id, ... other columns.... IMHO idName could support this syntax. (didn' t try yet and wouldn't fit the docu) for PK's with non numeric values concatenating ascii(text) for each letter of the PK would also generate a unique id making it suitable as unique numeric id. would be happy to discuss this further. -- cu Ferdinand ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
