On 4 Sty, 20:23, tofer...@gmail.com wrote:
> On 03.01-02:10, Szymon wrote:
> 3. you will need to substitute quotation marks, mysql uses ""
> and postgresql uses \". good old 'sed' to the rescue here.
This is not only difference - MySQL uses 0/1 for BooleanField,
Postgres t/f.
After two
On 03.01-02:10, Szymon wrote:
[ ... ]
> So there is any other working solutions for migrating MySQL ->
> Postgre?
i would suggest that you do this via the database not via django.
simply alter your 'settings.py' to point to your new postgres database
and sync it to create all the relevant
I'm working on a project that is doing this and wrote a data migration
script. The gist of it is that it connects to the old MySQL database
using straight MySQLdb, and connects to the new Postgresql database
using Django and the ORM. I iterate over all tables and such and call
my ORM methods to
Not the most exciting, but you could always use the orm to pull data
out of the old db and thenswl to put it into the new one(or vice
versa).
On Jan 3, 4:10 am, Szymon wrote:
> Hello,
>
> I've found in archives message:
>
> > Check out django_extensions
> >
Hello,
I've found in archives message:
> Check out django_extensions app,
> http://code.google.com/p/django-command-extensions/.
> It has a command, dumpscript [...]
It takes ages to complete. I've tried that method yesterday. I've
turned off my web server and ran that command. After 6 hours
5 matches
Mail list logo