On Sun, 2009-03-08 at 21:58 -0700, Matt Doran wrote: > Hi there, > > I'm porting another system across to Django, and I need to create a > multi-column unique index. I previously used SQLObject which has a > syntax for doing this. > > I came across this old post that said it wasn't possible and it > referred to creating custom backend SQL. > > > http://groups.google.com/group/django-users/browse_thread/thread/b789e7fa56d778ca/efd5f2f6d766e785?lnk=gst&q=multiple+column+index#efd5f2f6d766e785 > > The link to the documentation, no longer seems to contain the right > info. I found this: > > http://docs.djangoproject.com/en/dev/howto/initial-data/ > > ... which seems to do the job, but means I need to define the SQL for > each backend type.
Your application is only going to run on one backend, so focus on that. Also, if you're doing anything complex in custom SQL, use the post_syncdb signal, rather than the initial data hooks. The latter hooks don't contain a full SQL parser (and we have no intention to extend it more than it is), so it can be confused for complicated things. For index creation, it's probably fine. But if you get to the point of wanting to add triggers or something, then use post_syncdb signal handlers. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
