Depends on what kind of concurrency you are expecting. Simple answer is to just lock the table for queue updates. Another option is to do it with serializable transactions, but you'll have to handle serialization errors, and your database will pretty much halt and catch fire if you get heavy contention on queue removal.
Another way would be to build upon PgQ from the SkyTools package, assuming Postgres is an option. This gets you high performance and high concurrency with ACID reliability, but you'll have to handle the annoying possibility of getting items multiple times. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
