On Thu, Aug 8, 2013 at 9:22 PM, Larry Martell <larry.mart...@gmail.com> wrote: > So all I can do is execute sql > queries against it.
good news: that's all the ORM needs. :-) still, i've found myself on some situations where getting the ORM to work correctly wasn't worth the effort. mostly because of badly configured charsets on the server and existing data, so i couldn't get unicode text. in the end, i settled for just using py-odbc to access the MS-SQL Server tables (in latin1, ugh) and the ORM for the 'main' MySQL data. so, if you're lucky, you should just be able to set an ORM access to both servers. if not, there's nothing in Django to prevent you from using py-odbc. -- Javier -- 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 django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
