postfetch_cols() only applies to INSERT and UPDATE statements where defaults might have been fired off. Currently the execution context doesn't take the step of placing a blank collection (or raising an error) in the case of statements where this collection does not apply.
On Jun 8, 2012, at 7:24 AM, CJ Lee wrote: > I've looked in the source sqlalchemy/engine/base.py under the class > ExecutionContext and it does not contain this method postfetch_cols() > as documented. I've checked in 0.7.7, 0.6.9 stable versions as well as > 0.8 am I being silly and missing something? > > Details here: > http://stackoverflow.com/questions/10924160/sqlalchemy-executioncontext-postfetch-cols-doesnt-exist/10924329#10924329 > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
