On Fri, Oct 31, 2008 at 6:29 AM, varikin <[EMAIL PROTECTED]> wrote:
>
> Check out django_extensions app,
> http://code.google.com/p/django-command-extensions/.
> It has a command, dumpscript, which creates a python script to
> populate the database. That might get ride of the incompatible types.
On Oct 30, 1:57 pm, "Naitik Shah" <[EMAIL PROTECTED]> wrote:
> I ran into issues with this approach as well - first uniqueness constraints
> were failing, which I managed to fix manually. Next I got ContentType
> matching query issues, which I have not fixed yet.
>
> I was hoping to come up
I ran into issues with this approach as well - first uniqueness constraints
were failing, which I managed to fix manually. Next I got ContentType
matching query issues, which I have not fixed yet.
I was hoping to come up with a generic migration process since I have a few
other sites on MySQL.
This doesn't work as expected. I tried the migration with dumpdata
month ago.
The problem is, that mysql and postgres writes another, incompatible
boolean values. I believe sqlite and postgres has the same problem!
I reworked the dumpdata output-file. In my case this was possible,
because the
Why not just dump the data using manage.py dumpdata, switch your
settings file to point to the new DB, run syncdb, and then use
manage.py loaddata to get it all back? That should be pretty easy.
-David Christiansen
On Oct 30, 2:39 am, "Naitik Shah" <[EMAIL PROTECTED]> wrote:
> I looked around
I looked around but didn't find anything obvious or simple. This is a live
Django app with data in MySQL which I want to migrate to PostgreSQL.
Suggestions? (Before I do my own thing :))
-Naitik
--~--~-~--~~~---~--~~
You received this message because you are
6 matches
Mail list logo
