On Thu, Jan 12, 2012 at 10:03 AM, Demetrio Girardi <demetrio.gira...@gmail.com> wrote: > I have already done this previously, however in this case the table > has a multiple field primary key, unsupported by Django. There is no > other field which is guaranteed to be unique that I can use as primary > key in the Django model. > > Do I need to worry about this? or can I just slap the primary_key flag > on any of the fields, since I will never be inserting or updating in > that table?
maybe since it's read-only you could create a view with a field that concatenates the parts of the composite key -- Javier -- 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.
