The question is going to be very database specific. "select for update" works by putting in row-level locks in the database. If the row does not exist, then it won't get a lock on it, and I know of no databases that will maintain the query so that any newly created rows automatically get a lock on it.
However, not all is lost here. When you create new rows, those rows are _invisible_ to any other transaction until you do a commit. So, as long as you arrange things so that there's a final commit after you've done all the manipulations you want, you won't have those rows stomped on by any other transaction. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/nZcB89jwNb4J. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
