On Sat, Sep 4, 2010 at 4:45 PM, Andy <selforgani...@gmail.com> wrote: > What are the downsides of just importing & using SQLAlchemy (which > supports composite PK) in a Django program?
Essentially you lose integration of models with the rest of Django. Most importantly, this means ModelForms and Admin. It may also limit your ability to use existing reusable applications. However, basic view processing, URL dispatch, non-model forms and most other parts of Django that don't have model interactions will all work as is. You may also be able to implement some form of hybrid; using Django models for the models that don't require composite primary keys, but SQLAlchemy for the models that do. In this setup, you would only lose admin and forms for the models that don't have a Django representation. You may also need to jump through some interesting hoops in order to get foreign keys working between models represented in the two systems. Ultimately, you have to make a value call based on your own needs. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
