One approach may be to use django-import-export <https://django-import-export.readthedocs.org/en/latest/> to add to the admin interface the capability to export your data to CSV (or JSON or Excel) and likewise to import it. Then, simply run two instances of your app: one on top of postgres, one on top of sqlite. Export from one and import into the other.
Modifying the admin interface is probably not the fastest route to victory, but if your application is centered around uploading and downloading data, then you might decide that adding an "export to CSV" button is already useful. On Fri, Feb 20, 2015 at 4:55 PM, talex <bkielhor...@gmail.com> wrote: > Thanks for your helpful comments. > > Andrew, thanks for your migration article at http://afrg.co/updj17/a2 . > It is slightly daunting for me at this point, but I may need to come back > to it later. Your book looks interesting. > > Mike, thanks for the dump/load load suggestion. > > For the moment, I think the easiest thing for me is to follow Thomas, and > just start over with Postgres, but let me explain more about what I am > doing and ask two more questions. > > I am leading a project to create a web application for uploading certain > scientific data into a database. No one in the group has experience with > web development. We decided on Django, and I wrote a prototype using > sqlite3. Sqlite3 will not be used going forward. Instead either Postgres > or MySql will be used. Personally I am in favor of Postgres, but I have > been telling the group, perhaps incorrectly, that Django is "database > agnostic" and that we can easily change databases at any time in the future > should we need to do so. So let me ask two more questions: > > In the life of a Django application, is it simple and easy to change the > database flavor (say from Postgres to MySql), even after significant data > has accumulated in the model's database? > > Does the answer change if we are willing to forgo the use of the > version-control-like capabilities represented by Django's > makemirations/migrate tools? > > Thanks. > > > > > > > > > > > > > >> >> >> >> >> >> -- > 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+unsubscr...@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/458baa37-5387-4784-97c2-c7cbb50fc480%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/458baa37-5387-4784-97c2-c7cbb50fc480%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@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/CA%2By5TLY7v65oBPbsjW17ByqW4%3DGJTE359zo%3DqsGdEZKsEHm_uQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
