How to manage ordered db calls

[perryworks]

I haven't been able to find any reference to being able to manage order of operations for database calls. For example. I need to perform two sql statement based operations, A and B. A must be executed first, and B is dependent on the changes A made to the database. My instinct is to yield or await some kind of result message from SimpleSQLManager, but as far as I can tell, db operations are sent to the database, and no response is actually guaranteed. It also appears that the database is accessed on the main thread of the application? In other words if you perform some HUGE select query, your application will hang up. Would appreciate some clarification on these points. Thanks!

[echo17]

Yes, by default SimpleSQL is calling commands on the main thread. That is by design to avoid concurrent calls overlapping and causing unexpected behavior. I have not attempted multi-threaded calls before, but it looks like someone else has here: link. You might need to modify the source to accommodate this. Please see this FAQ for more information: link