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
-- 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/42ee3e9e-3d64-453f-9d6a-53846bec95e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment