Thanks for the update. This is very useful information.
On May 10, 9:41 pm, Karen Tracey <[email protected]> wrote:
> On Sun, May 10, 2009 at 8:45 PM, tekion <[email protected]> wrote:
>
> > Yes. I saw this link. My impression on first read is that it imports
> > the database into Django's database. I am not looking for this. I am
> > looking to just be able to read in the data from the external database
> > and leave the maintenance of the database to the external
> > application. Has anyone done gone done this path with Django. If
> > not, then I am thinking of writing my own code to generate the report
> > and just use Django for displaying the data. Thoughts?
>
> I think you may be misunderstanding that page. inspectdb looks at your
> existing database tables and generates Django models that you can use to
> access those tables. If you only want to query those tables, then you can
> do that. You can still use whatever other methods you have in place to
> update the existing tables, and your Django code that uses the generated
> models will see the updates. That is, inspectdb does not do any sort of
> 'import' from one DB to another, it simply provides a start at the Python
> code you need to access your existing tables from a Django application.
>
> Now, if you are going to be using Django-included apps like authentication,
> admin, and session support, those apps require their own tables and (at
> least until multi-DB support is added) those tables will need to be added to
> your existing database. You cannot currently easily segregate tables for
> one app into one DB and tables for another app into another DB.
>
> When I started with Django I was looking to add a web front-end to my
> existing database. I already had other tools to update the DB and was not
> interested at that point in doing any updates from Django, I just wanted a
> web front-end to see the data in ways I could not using my other tools. I
> was also pretty paranoid about letting this new untrusted tool change any of
> my existing data, so I set up the database user I specified in settings.py
> to not have any privileges that would let Django code make any changes to my
> existing tables. So you can use Django for read-only access to existing
> tables....I did it for quite a while, until I decided to migrate my update
> tools to a Django/web interface as well.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
