On Wed, Jun 4, 2008 at 6:37 AM, puff <[EMAIL PROTECTED]> wrote:
>
> The original code used a loop as you illustrated for the delete.
> Although I no longer have the original code, the annotated traces (see
> below) show the delete code in xx_xxraid was NOT invoked. This
> strikes me as at least
The original code used a loop as you illustrated for the delete.
Although I no longer have the original code, the annotated traces (see
below) show the delete code in xx_xxraid was NOT invoked. This
strikes me as at least a deficiency if not a bug.
initializexxNode
todo: tell SS delete
It is my understanding that the delete method you are calling is a
QuerySet method, not a model method, and thus there is nothing
overriding it. I'm sure that if you did this:
for x in xxRaid.objects.all():
x.delete()
Then your method will be called as desired. The overrides are for the
An hour later I know what caused the behavior and it seems to me to be
a Django bug or at least deficiency.
This behavior occurred during an initialization of the application.
First the table xx_xxnode was initialized by deleting all of its
records and then reloading the table from an external
RAW sql statement SELECT COUNT(*) FROM `xx_xxraid` shows table has 12
records.
In application statement
print '---xxx raids have', ESRaid.objects.count()
prints 0! Why?
I've imported connections and
print connection.queries[-1]
just after the count prints
{'time': '0.000', 'sql':
5 matches
Mail list logo
