Thanks.
I suspect this is the issue, as I just changed the settings.py file on
the original project to point to the copied database file. It has no
problem accessing the data. I'll play around with the meta settings
and see what I can come up with.
Thanks!
On Jan 25, 3:46 pm, Michael <mhall...@gmail.com> wrote:
> The database tables are named {{app_label}}_{{model_name}}, so in order
> to use the same database you will need to use the same application name
> (or specify db_table in the model's Meta).
>
> --
> Michael <mhall...@gmail.com>
>
>
>
>
>
>
>
> On Tue, 2011-01-25 at 07:36 -0800, Ben Dembroski wrote:
> > Hi all,
>
> > Afraid I've got another newbie question. I've been doing some
> > development on a project using sqlite3. All is working well, and I'd
> > like to use the same database file in another project, data intact.
> > I've copied the database file, and the models.py file to the
> > appropriate locations in the new project. When I run syncdb, the
> > only result is 'no fixtures found.'
>
> > When I pop into the shell, all the fields are there, but I can't get
> > to the data in any of them.
>
> > For instance, inside the shell for the new project I run:
>
> > Person.objects.all()
>
> > it returns
>
> > []
>
> > Do I need to do something besides just copying the database file to
> > keep my data, provided the models.py files are unchanged?
>
> > Many thanks,
> > Ben
--
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.
