Hi, I take it doing via JSON you still need to convert the Boolean fields?
would you know of any kind of scrip that would do it? as my editor doenst cope to well with 7mb of xml files :(. I guess its not to hard to write if needed. I do a syncdb than run loaddata, I didnt empty the tables, will do that thou, makes sence (I thought loaddata overwrite the "tables"). thanks for the info! On May 19, 7:20 pm, AndrewK <[EMAIL PROTECTED]> wrote: > AFAIK, you will probably need to do conversion between boolean types > (in MySQL BooleanField uses 0 and 1, and in PostgreSQL it uses True > and False). > I was doing it with JSON. And then you will need to empty all tables > like django_content_type and auth_permission in the target db or > exclude them from your dump. > First method (transfer this tables) is better especially if you were > doing some tweaking with your db (like adding, removing models) > > On May 19, 1:41 am, oliver <[EMAIL PROTECTED]> wrote: > > > Hi, > > I am planning to move from Mysql to PostgreSQL (mainly for transaction > > support). I just wanted to know if I can take my active django > > projects (all with lots of data in mysql, with more or less every > > model field type possible) and do a XML data dump and than just load > > this into the Postgresql db? > > > I have been reading about differences in how Mysql stores boolean > > fields against Postgresql? Would I need to change any thing in the > > xml? or does django take care of all this? > > > Or is there some "smarter" way of doing this db change over? > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
