On Thursday, 8 November 2012 05:58:50 UTC+2, Cliff Kachinske wrote:
Version 2.0.9, Postgres 9.X, Psycopg2
I don't know what else to tell you, except I know the record was there
after the failed delete attempt.
Did you do a
db.commit() ?
Regards
Johann
--
try with 2.2.1, it's the one I tested
On Thursday, November 8, 2012 4:58:50 AM UTC+1, Cliff Kachinske wrote:
Version 2.0.9, Postgres 9.X, Psycopg2
I don't know what else to tell you, except I know the record was there
after the failed delete attempt.
Today the same syntax failed in
Shouldn't have to commit, since I'm not working from the console.
On Thursday, November 8, 2012 5:21:17 AM UTC-5, Johann Spies wrote:
On Thursday, 8 November 2012 05:58:50 UTC+2, Cliff Kachinske wrote:
Version 2.0.9, Postgres 9.X, Psycopg2
I don't know what else to tell you, except I know
The record was there.
That's the problem. The shortcut was erroneously reporting that it was
gone.
On Tuesday, November 6, 2012 2:40:38 PM UTC-5, Niphlod wrote:
del db.sometable[something] requires that the id == something exists.
db(db.sometable.id == something).delete() instead returns
but I tried in a shell and it doesn't raise an exception if the record
exists (and it gets correctly deleted too)
On Wednesday, November 7, 2012 1:59:48 PM UTC+1, Cliff Kachinske wrote:
The record was there.
That's the problem. The shortcut was erroneously reporting that it was
gone.
On
Version 2.0.9, Postgres 9.X, Psycopg2
I don't know what else to tell you, except I know the record was there
after the failed delete attempt.
Today the same syntax failed in another location in my code, with the same
result. I thought I caught them all, but apparently not.
On Wednesday,
del db.sometable[something] requires that the id == something exists.
db(db.sometable.id == something).delete() instead returns the number of
records deleted if there was any, otherwise it simply deletes nothing.
On Tuesday, November 6, 2012 8:14:33 PM UTC+1, Cliff Kachinske wrote:
This code
7 matches
Mail list logo
