> The biggest is the single column primary key. If you're working on > legacy databases, multi-column primary keys are fairly common. Other > limitations can be worked around with _get_ and _set_ hacking (though > it's ugly) but this cannot.
Ok, I'm a friend of single-column primary keys anyway, but of course one _might_ come into a situation this isn't avoidable. > If you don't mind reading, I believe that most items in the advanced > datamapping[1] section of the SA docs are difficult to do. It's > getting hard to remember the details, I've been switched over since > February (due to the primary key issue). > > [1] http://www.sqlalchemy.org/docs/adv_datamapping.myt > > One particular SA feature that I'm happy about is the associationproxy > extension[2], which Michael just put in SVN (because I was harassing > him about it ;]). It's a bit strange to get your head around, but it > allows you to implement typed relationships (I use them for user > roles) between two tables without having to manage the association > objects yourself. > > [2] http://www.sqlalchemy.org/docs/plugins.myt#plugins_associationproxy Thanks for the pointers, and of course I'm willing to read :) Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
