On Fri, Jan 23, 2015 at 7:20 AM, SF Markus Elfring <elfr...@users.sourceforge.net> wrote: >>> I would appreciate if I can fill these data structures in parallel >>> without a serial database preparation step (table creation with >>> repeated meta-data specification). >> >> You’d need to implement checks for this concurrency. > > I would expect that database implementations will provide functionality > for parallel updates including concurrent creation of each table. >
What would you expect a database to do if it receives 2 "CREATE TABLE my_table(...)" instructions simultaneously? What if the table definitions are different? One of the instructions would *have* to fail. > >> A create table would need to be preceded by a check to see that it exists, >> for example, and that would likely need to be mutexed on that name so that >> no race condition occurs in between the time that the name is checked >> vs. the create table is emitted. > > I am curious to clarify more software development challenges. > How many open issues are already known around such implementation details? > > Regards, > Markus > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
