works fine.... good solution... but why this happens with posgres and don't with sqlite ??
in my country this is know as GAMBIBARRA ... but it's ok =)
anyway, thanks for this post!
Thanks, this seems to be the only page on the whole internet that provides a solution for this nonsensical error.
I'm also curious as the why this only happens with PostgreSQL, but not MySQL.
It's not so much that postgresql "treats" it as a transaction but that Django developers obviously decided to use the transaction mechanism that PG offers, maybe for safety reasons.
It should be documented more clearly though, and maybe given a choice to the user.
Comments
works fine.... good solution... but why this happens with posgres and don't with sqlite ?? in my country this is know as GAMBIBARRA ... but it's ok =) anyway, thanks for this post!
Thanks, this seems to be the only page on the whole internet that provides a solution for this nonsensical error. I'm also curious as the why this only happens with PostgreSQL, but not MySQL.
The reason that the postgresql treat a sql command as a transaction.
It's not so much that postgresql "treats" it as a transaction but that Django developers obviously decided to use the transaction mechanism that PG offers, maybe for safety reasons. It should be documented more clearly though, and maybe given a choice to the user.
where do you put this code import django django.db.connection.close()