Yup. That did it. The errors were a result of setttings.py pointing to
the wrong database.
Too much mucking about with too many things at the same time...
On 25/01/11 16:36, Michael wrote:
I believe table names are all lower-case, so try 'sample_app_person'
--
You received this message bec
That solved the syncdb error, but I'm still getting the same error
inside the shell when I am trying get to the data.
Progress!
Thanks again!
On 25/01/11 16:36, Michael wrote:
I believe table names are all lower-case, so try 'sample_app_person'
--
You received this message because you are
I believe table names are all lower-case, so try 'sample_app_person'
--
Michael
On Tue, 2011-01-25 at 08:33 -0800, Ben Dembroski wrote:
> Attempting to add the db_table name to the model made things a bit
> more confusing.
>
> The original app's name was 'sample_app' (not my choosing)
>
> The
Attempting to add the db_table name to the model made things a bit
more confusing.
The original app's name was 'sample_app' (not my choosing)
The app that I'm trying to get to access the data is 'trajectories'
I just added the following the Meta class for one of the models:
class Meta:
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 wrote
On Tue, Jan 25, 2011 at 10:36 AM, Ben Dembroski wrote:
> When I run syncdb, the
> only result is 'no fixtures found.'
in Django-speak 'fixtures' are external files with data to be inserted
in the database, could be in XML, JSON or YAML. do you use them?
maybe you should copy those too from your
> 've copied the database file, and the models.py file to the
> appropriate locations in the new project.
Have you adjusted the settings.py database settings to the correct values ?
If so, maybe try the full path to your database file.
Regards,
Jonas.
--
You received this message beca
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
On Tue, 2011-01-25 at 07:36 -0800, Ben Dembroski wrote:
> Hi all,
>
> Afraid I've got another ne
Do you have suitable file system permissions on the db file for use in
the new context?
Are the two usages (if they are on different machines, or in different accounts)
using the same version of sqlite? (I don't know enough about sqlite to know if
this is a problem, but it's worth checking.)
Doe
9 matches
Mail list logo
