Il giorno lunedì 23 settembre 2013 02:57:31 UTC+2, Jonathan Lundell ha scritto: > > Suppose I have a list of Row as the result of a select, and I want to > delete those records. > > I can't delete the Set, since it might not be the same rows (the query has > a limitby, and more records might have been inserted since I processed the > result of the select; I don't want to delete the unprocessed records). > > The best I can think of is to create a new Query of the form > table.id.belongs(<list of id's in the Rows>). Is there a better way? > > That is what I'd do too.
> > And a semi-related question. If I do a select, and delete the resulting > rows, and then do the same select without doing a commit (in the same > request, that is), will the second select "see" the (uncommitted) deleted > row? > > you should not see them. "Inside" a transaction you see "the current version of reality" while you modify it, so as long as nobody else inserts new records, any deleted record won't be available anymore. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
