I'm not sure this is of help but I took was the easy way out. In my
models.py for each of my models.Model I added
Class Meta:
managed = False
That worked for me - the existing database tables were not touched.
Johnf
On 03/06/2015 01:18 PM, Robert Daniels wrote:
> I understand it is possible to use an existing database on a new
> Django project.
>
> As I see it, I have 2 choices.
>
> 1 - Use the existing database and deal with it in that fashion.
>
> or
>
> 2 - Create a new project to store the same type of data as if there
> were no existing database, Then write a separate export-import script
> to move the data from the existing db to the new structure.
>
> Wondering if anyone has gone through the "good" and "bad" of each of
> these. I have about 100,000 records in the database, but moving the
> data across should not be that difficult as its a pretty flat model
>
--
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+unsubscribe@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.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/54FA3B50.1010707%40jfcomputer.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment