On Fri, Sep 19, 2008 at 6:05 PM, Bas van Oostveen <[EMAIL PROTECTED]> wrote:
>
> And would be as easy to implement, the possible usecases i've got is
> with a big fixture of a organism/protein database. This can be
> compressed very well and is only applied one, so no need to keep a 50+
> MB fixtu
I agree with Russ Magee's feeling.
For compression you should just use pipes, you already pipe the output
to a file, you should also pipe it through a compress app.
An -c,--compress option does not make any sense without an accompanying
-o,--output-file option as well.
Though i'm +1 on having t
I have a use case for compressed fixtures too.
> Jeremy Dunck wrote:
>> I'd like to add support for fixture load/dump to deal with compressed
>> (gzip) files transparently.
Jacob Kaplan-Moss wrote:
> I don't see a good reason *not* to do this, but I also don't see the
> space requirements as a b
On Sat, Sep 13, 2008 at 1:35 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> I'd like to add support for fixture load/dump to deal with compressed
> (gzip) files transparently.
Something like #4924, perhaps? :-)
I'm not completely sold on the --compress option to dumpdata - there
are many option
On Sat, Sep 13, 2008 at 6:35 AM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> I'd like to add support for fixture load/dump to deal with compressed
> (gzip) files transparently.
I don't see a good reason *not* to do this, but I also don't see the
space requirements as a big deal, either; disk space
I'd like to add support for fixture load/dump to deal with compressed
(gzip) files transparently.
# django-admin.py dumpdata --compress > foo.json.gz
# django-admin.py loaddata foo #looks for foo.json, foo.json.gz, etc.
# django-admin.py syncdb #looks for initial_data.json,
initial_data.json.gz,
