I need to write a small application and considering django but am wondering how the model backend copes with the following scenario..
The admin user needs to be able to upload/download new dbs and switch the current backend database file and run the app portably on different machines. The concurrent number of users is very small (1-5 people) so was thinking of sqlite as a single file then contains the whole db. DB related requirements: 1. select the current working DB from any DB files in the app's DB directory 2. upload/download any of those DBs (for backup/restore and swapping DBs between offices) 3. Create a new empty DB file to start working from. This doesn't seem to naturally fit django's idea of specifying the db in the settings file but is there a way to do this that is not too much of a nasty hack! I would like to do it in django because I know the rest of the app would be quick to put together with django but am a little concerned about how these requirements fit with the model engine. Any advice? Thanks in advance, John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
