On 9/6/07, Paul Davis <[EMAIL PROTECTED]> wrote:
> I think the biggest issue is the fact that:
> $ python manage.py sqlcustom appname
> gives sql thats in a transaction. It was confusing to have the two
> different behaviors.
Ah - interesting. That should probably be raised as a bug (with a
sugg
On 9/5/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 9/6/07, Paul Davis <[EMAIL PROTECTED]> wrote:
> >
> > I'm having a bit of a problem using the appname/sql/model.sql custom
> > sql files.
> ...
> > But running:
> > $ python manage.py sqlcustom root | psql eureka
> >
> > Completes wi
On 9/6/07, Paul Davis <[EMAIL PROTECTED]> wrote:
>
> I'm having a bit of a problem using the appname/sql/model.sql custom
> sql files.
...
> But running:
> $ python manage.py sqlcustom root | psql eureka
>
> Completes wihtout errors. So, I'm fairly certain that the custom sql
> is not being run in
I'm having a bit of a problem using the appname/sql/model.sql custom
sql files.
Running:
$ python manage.py syncdb root
Gives:
Installing custom SQL for root.Status model
Installing custom SQL for root.Target model
Installing custom SQL for root.Reference model
Installing custom SQL for root.Seq
