On Wed, Jun 3, 2009 at 8:13 AM, Alex Gaynor <alex.gay...@gmail.com> wrote: >so the question is: if i don't define a pk for an >> existing table, there will be problems in the application? for example >> when deciding if a save() should be an insert or an update? >> > > Django does not currently support multiple column primary keys, see: > http://code.djangoproject.com/ticket/373 >
good database design makes use very often of composite pk's so my best bet is to declare the models without a primary key and make my code decide if an UPDATE or an INSERT is needed? -- Atentamente, Jaime Casanova Soporte y capacitación de PostgreSQL AsesorÃa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
