Thanks for all the advice! I think django could probably do with a
little tool like this when dumping or importing data.
Is the boolean field the only odd one out? or is there any thing else
that needs chanaging? Date fields? datetime?
Thanks again!
On May 20, 12:54 pm, George Vilches <[EMAIL P
Hanne Moa wrote:
> I have a filter that makes django's json-dumps more human-readable, by
> adding a newline after every occurence of "}},". Running such a filter
> first would make for short and snappy lines for the rewriting filter:
>
> python manage.py dumpdata | prettifyjson | fixbooleans > p
On Tue, May 20, 2008 at 10:32 AM, oliver <[EMAIL PROTECTED]> wrote:
> 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
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
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 fr
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
6 matches
Mail list logo
