- merged inline inserts branch

- all executemany() style calls put all sequences and SQL defaults inline into a single SQL statement
and don't do any pre-execution
- regular Insert and Update objects can have inline=True, forcing all executions to be inlined.
- no last_inserted_ids(), lastrow_has_defaults() available with inline execution
- calculation of pre/post execute pushed into compiler; DefaultExecutionContext greatly simplified
- fixed postgres reflection of primary key columns with no sequence/default generator, sets autoincrement=False
- fixed postgres executemany() behavior regarding sequences present, not present, passivedefaults, etc.
- all tests pass for sqlite, mysql, postgres; oracle tests pass as well as they did previously including all
insert/update/default functionality

1 files changed, 8 insertions, 1 deletions

diff --git a/test/sql/select.py b/test/sql/select.py
index fa5e3af03..5eaea7480 100644
--- a/test/sql/select.py
+++ b/test/sql/select.py
@@ -1125,7 +1125,14 @@ class CRUDTest(SQLCompileTest):
             "INSERT INTO mytable (myid, name) VALUES (:userid, :username)"
         )
     
-        
+    def testinlineinsert(self):
+        metadata = MetaData()
+        table = Table('sometable', metadata, 
+            Column('id', Integer, primary_key=True),
+            Column('foo', Integer, default=func.foobar()))
+        self.assert_compile(table.insert(values={}, inline=True), "INSERT INTO sometable (foo) VALUES (foobar())")    
+        self.assert_compile(table.insert(inline=True), "INSERT INTO sometable (foo) VALUES (foobar())", params={})    
+            
     def testinsertexpression(self):
         self.assert_compile(insert(table1), "INSERT INTO mytable (myid) VALUES (lala())", params=dict(myid=func.lala()))