>> 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?
This depends on the passed parameters. > What if the table definitions are different? I am going to pass the same settings for the application I am developing at the moment. > One of the instructions would *have* to fail. Not in every case. The parameter "IF NOT EXISTS" could be passed to the SQL statement "CREATE TABLE". * Is this setting already used by the class library "SQLAlchemy 0.9.8-78.1"? * Does it really work in the current praxis? 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.
