Thanks - I'll try this out on a fresh DB. You're right that I'm running
sqlall on an already populated database.
I'll post back if it looks like there was a real bug here.
Thanks again for all of your help,
Greg
Russell Keith-Magee wrote:
> On 10/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> w
Waylan Limberg wrote:
>> Do any of you know if there's a way to tell Django to specify "on
> cascade delete" for foreign key references, when it creates DB tables?
>
> I don't believe you can. However, you can use sql or sqlall [1] to
> output the table creation sql to a file for editing. For ex
All,
Do any of you know if there's a way to tell Django to specify "on
cascade delete" for foreign key references, when it creates DB tables?
I'm developing an application that is mostly using Django to touch my
DB, but that defines some SQL stored-procedures for manipulation of some
of its d
That does fix it - thanks Michael.
I just want to summarize what I'm seeing, though, in case it helps others:
- In no place, either in my MySQL shell or my Python Django session,
am I explicitly starting a transaction. Further, my MySQL shell has
auto_commit on.
- If I make a change in t
y by other clients.
Michael Radziej wrote:
> Greg Plesur schrieb:
>> Hi all,
>>
>> I'm a new subscriber to this list, and am having an issue that I'm
>> hoping you can help me with (I also posted this as a trouble-ticket,
>> because I'm not seeing an
Don,
Don Arbow wrote:
> Did you read this documentation, especially the last line of this paragraph?
>
> http://www.djangoproject.com/documentation/db_api/#id3
>
> In a newly created QuerySet, the cache is empty. The first time a
> QuerySet is evaluated -- and, hence, a database query happens
Hi all,
I'm a new subscriber to this list, and am having an issue that I'm
hoping you can help me with (I also posted this as a trouble-ticket,
because I'm not seeing any references to this issue anywhere and it
seems buggy):
It looks like my models are caching their DB query in a way that I
7 matches
Mail list logo
