> > Hi Mike,
Thanks for the suggestion. Yes, postgres would be a good answer, but not really a possibility at this point. Let me give you the back ground. I inherited this project. The original project is written using django 0.95 and SQL Server 2003. The project that was written by a long departed employee in 2009. Several other systems have started using the data in this database. Unless I want to update all of them to use the postgres, I'm stuck with MS SQL Server 2012. I'm also a big fan of not fighting your tools... -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/6df5929e-48b0-4b04-98ac-9f56f309330f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
