On Thu, Oct 6, 2011 at 8:37 PM, Lars Ruoff <lars.ru...@gmail.com> wrote: > Hi, > > i'm having the Django database set up like so: > DATABASES = { > 'default': { > 'ENGINE': 'django.db.backends.sqlite3', > 'NAME': 'D:\Users\Max\Projects\my4x\data\my4x.db', > 'USER': '', # Not used with sqlite3. > 'PASSWORD': '', # Not used with sqlite3. > 'HOST': '', # Set to empty string for > localhost. Not used with sqlite3. > 'PORT': '', # Set to empty string for > default. Not used with sqlite3. > } > } > > I see that the database contains a lot of Django-related stuff (tables > with auth_ and django_ prefixes). > Is there a way i can seperate the Django stuff from my apps model > database? > What I'd prefer is to have two different databases (files), with one > containing the Django stuff and the other my own models. > Reason is that i develop a game and the database stores the game state > for a given time step. Ideally, i would like to have a different game > database file for each time step so i can go back in time when i like. >
Django will happily support multiple databases, see the docs for the caveats. https://docs.djangoproject.com/en/1.3/topics/db/multi-db/ Cheers Tom -- 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.