#5578: Can't import fixtures generated using mysql into postgresql
------------------------------------------------------------------------+---
Reporter: [EMAIL PROTECTED] |
Owner: nobody
Status: new |
Component: Database wrapper
Version: SVN |
Resolution:
Keywords: postgresql mysql case sensitive sensitivity fixture load |
Stage: Unreviewed
Has_patch: 0 |
Needs_docs: 0
Needs_tests: 0 |
Needs_better_patch: 0
------------------------------------------------------------------------+---
Changes (by ubernostrum):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Old description:
> Fixtures generated using an app running against mysql can't be imported
> by that same app if switched to run against postgresql. This appears to
> have to do with different handling of mixed case table/column names in
> django's drivers for the two databases.
>
> Here's the error I get. The same error occurs regardless of fixture
> format. Note the case difference between
> spackle1_projecttemplate_subjectareas (from the exception) and
> spackle1_projecttemplate_subjectAreas (from the sql):
>
> Loading 'spackle1/fixtures/spackle1' fixtures...
> Installing xml fixture 'spackle1/fixtures/spackle1' from absolute path.
> Traceback (most recent call last):
> File "./manage.py", line 11, in <module>
> execute_manager(settings)
> File "/usr/lib/python2.5/site-
> packages/django/core/management/__init__.py", line 264, in
> execute_manager
> utility.execute()
> File "/usr/lib/python2.5/site-
> packages/django/core/management/__init__.py", line 215, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 70, in run_from_argv
> self.execute(*args, **options.__dict__)
> File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
> line 84, in execute
> output = self.handle(*args, **options)
> File "/usr/lib/python2.5/site-
> packages/django/core/management/commands/loaddata.py", line 119, in
> handle
> cursor.execute(line)
> File "/usr/lib/python2.5/site-packages/django/db/backends/util.py",
> line 19, in execute
> return self.cursor.execute(sql, params)
> File "/usr/lib/python2.5/site-
> packages/django/db/backends/postgresql/base.py", line 47, in execute
> return self.cursor.execute(smart_str(sql, self.charset),
> self.format_params(params))
> psycopg.ProgrammingError: ERROR: relation
> "spackle1_projecttemplate_subjectareas" does not exist
>
> SELECT setval('"spackle1_projecttemplate_subjectAreas_id_seq"',
> coalesce(max("id"), 1), max("id") IS NOT null) FROM
> spackle1_projecttemplate_subjectAreas;
New description:
Fixtures generated using an app running against mysql can't be imported by
that same app if switched to run against postgresql. This appears to have
to do with different handling of mixed case table/column names in django's
drivers for the two databases.
Here's the error I get. The same error occurs regardless of fixture
format. Note the case difference between
spackle1_projecttemplate_subjectareas (from the exception) and
spackle1_projecttemplate_subjectAreas (from the sql):
{{{
Loading 'spackle1/fixtures/spackle1' fixtures...
Installing xml fixture 'spackle1/fixtures/spackle1' from absolute path.
Traceback (most recent call last):
File "./manage.py", line 11, in <module>
execute_manager(settings)
File "/usr/lib/python2.5/site-
packages/django/core/management/__init__.py", line 264, in execute_manager
utility.execute()
File "/usr/lib/python2.5/site-
packages/django/core/management/__init__.py", line 215, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
line 70, in run_from_argv
self.execute(*args, **options.__dict__)
File "/usr/lib/python2.5/site-packages/django/core/management/base.py",
line 84, in execute
output = self.handle(*args, **options)
File "/usr/lib/python2.5/site-
packages/django/core/management/commands/loaddata.py", line 119, in handle
cursor.execute(line)
File "/usr/lib/python2.5/site-packages/django/db/backends/util.py", line
19, in execute
return self.cursor.execute(sql, params)
File "/usr/lib/python2.5/site-
packages/django/db/backends/postgresql/base.py", line 47, in execute
return self.cursor.execute(smart_str(sql, self.charset),
self.format_params(params))
psycopg.ProgrammingError: ERROR: relation
"spackle1_projecttemplate_subjectareas" does not exist
SELECT setval('"spackle1_projecttemplate_subjectAreas_id_seq"',
coalesce(max("id"), 1), max("id") IS NOT null) FROM
spackle1_projecttemplate_subjectAreas;
}}}
Comment:
(cleaning up formatting in description)
--
Ticket URL: <http://code.djangoproject.com/ticket/5578#comment:1>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
