System.Diagnostic是通过查询WMI还是通过其他方式获取其数据？(Does System.Diagnostic get its data by querying the WMI or by other means?)

 当你执行一个纯文本语句时，你可以用你正在使用的DBAPI来控制新的PK值是否可用，以及通过什么方式。 使用SQlite和MySQL DBAPI，您可以将它作为result.lastrowid，它只会为您提供游标的.lastrowid值。 对于PG，Oracle等，没有“.lastrowid” - 正如其他人所说的那样，对于那些可以通过result.fetchone（）得到结果的用户，可以使用“RETURNING”（虽然在oracle中使用RETURNING， ），或者如果RETURNING不可用，则可以使用直接序列访问（NEXTVAL in pg）或“post fetch”操作（PG中的CURRVAL，@@ identity或scope_identity（） MSSQL）。 
 
 听起来很复杂吗？ 这就是为什么你最好使用table.insert() 。 SQLAlchemy提供新生成的PK的主要系统旨在与这些构造一起工作。 一个你在那里， result.last_inserted_ids()方法给你所有情况下新生成的（可能是复合的）PK，而不管后端。 以上的.lastrowid，序列执行，RETURNING等方法都是为你处理的（0.6使用RETURNING时可用）。 

When you execute a plain text statement, you're at the mercy of the DBAPI you're using as to whether or not the new PK value is available and via what means. With SQlite and MySQL DBAPIs you'll have it as result.lastrowid, which just gives you the value of .lastrowid for the cursor. With PG, Oracle, etc., there's no ".lastrowid" - as someone else said you can use "RETURNING" for those in which case results are available via result.fetchone() (although using RETURNING with oracle, again not taking advantage of SQLAlchemy expression constructs, requires several awkward steps), or if RETURNING isn't available you can use direct sequence access (NEXTVAL in pg), or a "post fetch" operation (CURRVAL in PG, @@identity or scope_identity() in MSSQL).
 
Sounds complicated right ? That's why you're better off using table.insert(). SQLAlchemy's primary system of providing newly generated PKs is designed to work with these constructs. One you're there, the result.last_inserted_ids() method gives you the newly generated (possibly composite) PK in all cases, regardless of backend. The above methods of .lastrowid, sequence execution, RETURNING etc. are all dealt with for you (0.6 uses RETURNING when available).