Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Django developers
Home
+ new post
About this group
Join this group
Message from discussion Changing the options in manage.py, adding more signals (was Re: Adding hooks to methods that generate SQL in django/core/management.py)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Russell Keith-Magee  
View profile  
 More options Aug 14 2007, 8:09 pm
From: "Russell Keith-Magee" <freakboy3...@gmail.com>
Date: Wed, 15 Aug 2007 08:09:38 +0800
Local: Tues, Aug 14 2007 8:09 pm
Subject: Re: Changing the options in manage.py, adding more signals (was Re: Adding hooks to methods that generate SQL in django/core/management.py)
Print | View thread | Show original | Report this message | Find messages by this author
On 8/14/07, George Vilches <g...@thataddress.com> wrote:

> George Vilches wrote:
> Unfortunately, since there's only a syncdb signal, I can't even do
> things like a reset on it, and there's definitely no way currently to
> get the SQL generated from my syncdb signal.  Being able to get the
> CREATE and DROP statements in text as well as each individually would be
> a huge boon to this type of use (and any dynamic model use in general).

> Is that a more reasonable example?

That maybe explains the need for a signal on reset - except that I'd
be an advocate for removing the reset command altogether. It's pretty
badly broken as it currently stands - any tables with m2m relations
will have some major difficulties using it (if you're using a database
with row referential integrity, anyway).

Getting access to the CREATE and DROP statements is a separate issue -
and was the reason for my suggesting the SQL logger. The idea would be
that you could call _any_ manage.py command with the --sql flag, and
you would get the SQL output to the screen, rather than the database.

Yours,
Russ Magee %-)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google