Hey Guys,
I'm about to start developing a web front-end for a large database being
developed by a colleague. The web front-end is only going to be
accessing a sub-set of the database, and mostly via 'views' that will be
specific to the requirements of the web frontend.
I want to use Django, since I'm vaguely familiar with it (and it rocks).
But what I want to do is have one database for all the django-specific
stuff, so that I don't have to create any django-specific tables in the
main database.
Can anyone point me in the direction of achieving this? Will I still be
able to take advantage of Django's database API or will I end up having
to drop to raw SQL a lot more?
I'm just kind of testing the waters at the moment. Anyone have any
experience in similar situations?
Thanks!!
Tom
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
