Lukasz Szybalski schrieb: > Hello, > So it seems as primary compound key with auto increment on a second > field does not work in innodb version of mysql db engine. > > What engine do you guys use for transaction heavy app with compound keys? > Do you auto increment within the program?
So far all schemas with compound keys I've seen didn't have auto-increment keys. To me, that's kind of mutually exclusive: either you don't care about the value of the key, then use autoincremented ids. Or you _do_ need it to be composed of data for whatever reason (to be honest: I _never_ saw that as something desirable, instead it only complicated things) - then that data should guarantee the uniqueness somehow (e.g. first/lastname, albeit that of course is a bad example - but I don't have a better one....) And neither design has to do with transaction heavyness. But apart from that, I do use postgres - which has sequence objects that could aid you. 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 -~----------~----~----~----~------~----~------~--~---
