Russell Keith-Magee wrote:
> On Fri, May 16, 2008 at 3:47 AM, Carl Karsten <[EMAIL PROTECTED]> wrote:
>> Russell Keith-Magee wrote:
>>> On Wed, May 14, 2008 at 1:20 PM, Carl Karsten <[EMAIL PROTECTED]> wrote:
>>>> Russell Keith-Magee wrote:
>>>>> On Wed, May 14, 2008 at 1:09 AM, Carl Karsten <[EMAIL PROTECTED]> wrote:
>>>> What are the chances of getting a dumpdata hack to exclude certain apps?
>>>>
>>>> I know it isn't too hard to figure out what apps I want to backup, but it
>>>> sounds
>>>> like the 'exclude' feature might be useful even once this issue is
>>>> resolved.
>>> It's a reasonable idea - one well worth suggesting as a feature
>>> enhancement (I have a nagging feeling that there is something in there
>>> already, but I could be getting confused).
>>>
>>> What are the chances such a fix will automagically materialize out of
>>> the ether? Not high. What are the chances that a patch implementing
>>> this feature would be added to trunk? Fairly good, conditional on the
>>> quality of the patch.
>> I am not submitting here, I just want to discuss it first.
>>
>> 1. what do you think of this syntax I invented:
>> --option "list of items"
>>
>> I don't like it, but not sure how else to do it.
>
> I prefer the syntax from your other post.
>
>> 2. should I leave in --debug? I really meant it for debugging, but I can
>> see it
>> being handy to debug the "list of items" and such.
>
> No. That's what the verbosity option is for.
what verbosity option?
./manage.py: error: no such option: --verbosity
./manage.py: error: no such option: --verbose
Given that dumpdata dumps to stdout, any extra chars would 'corrupt' the dump,
and the human readable 'status' chars would get lost in the dump. So I am not
sure --verbose would be good here, given that --verbose generally runs the app.
How about --dry-run?
>> Why does the current code has 'json' listed in 2 places:
>> make_option('--format', default='json'
>> options.get('format', 'json')
>
> I can't think of an obvious reason off the top of my head. It's
> possible that this is a hangover of some old code from the
> pre-management refactor days, or an artefact of that refactor.
I'll clean it up. Should the clean up be a separate patch?
Carl K
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
