COMMIT/ROLLBACK error after deleting device

[Ingeborg Hellemo]

When I delete a device I get an

"Error: Transaction managed block ended with pending COMMIT/ROLLBACK"

The device is deleted, but the error message (in red) is noisy and confusing.

NAV 3.9.3
postgresql-client-8.4.8
postgresql-server-8.4.8_1


--Ingeborg

[Morten Brekkevold]

Post by Ingeborg Hellemo
When I delete a device I get an
"Error: Transaction managed block ended with pending COMMIT/ROLLBACK"
The device is deleted, but the error message (in red) is noisy and confusing.

Is there a Python traceback on the page, or just a plain error message
above the IP Device list? If no traceback on the page, is there a
traceback in your Apache error log?

[Ingeborg Hellemo]

Post by Morten Brekkevold
Is there a Python traceback on the page,

No.

Post by Morten Brekkevold
or just a plain error message above the IP Device list?

Yes. In red letters.

Actually, when I see the error I am still on <https://nav.uit.no/seeddb/netbox/

Post by Morten Brekkevold
with my device listed (and checkbox crossed) and the "Confirm delete"-button

still in place.

If I then press "Confirm delete" once more I get
"Error: syntax error at or near ")" LINE 1: DELETE FROM "netbox" WHERE
"netboxid" IN () ^ "
because the device was deleted the first time.

Post by Morten Brekkevold
If no traceback on the page, is there a traceback in your Apache error log?

Nothing.

Sorry ;-)


--Ingeborg

[Morten Brekkevold]

Post by Ingeborg Hellemo
Actually, when I see the error I am still on <https://nav.uit.no/seeddb/netbox/

Post by Morten Brekkevold
with my device listed (and checkbox crossed) and the "Confirm delete"-button

still in place.
If I then press "Confirm delete" once more I get
"Error: syntax error at or near ")" LINE 1: DELETE FROM "netbox" WHERE
"netboxid" IN () ^ "
because the device was deleted the first time.

I did some checking, and just as in the alert profile issue you reported
in LP#906850 it appears this is Django-version related.

I'm unable to reproduce the problem under Django 1.2, which we use for
testing and development, but with Django 1.3 the problem readily
appears.

I suggest you report it as a Django 1.3 incompatibility issue in the
bugtracker.