On Sun, 23 Feb 2014, Michael Bayer wrote:
The overall behavior you're seeing is due to http://docs.sqlalchemy- .org/en/rel_0_9/changelog/changelog_09.html#change- 2df4f7fe29c0f5aa2f957f4a89b0d74d
Thanks very much for the quick response.
table.mysql_engine = 'InnoDB' should not be having any effect, that would be a bug. All of these options should be consumed by the dialect from the .dialect_options collection.
As my followup states I was being stupid. My test to see if it was working was busted. I had assumed if things didn't blow up it was working.
At the moment there is no "setter" interface for this new system so I've added to https://bitbucket.org/zzzeek/sqlalchemy/issue/2962/add-api-to-dialectkwargs-to-add-new for that.
Awesome, thanks for that.
The best practice here would be to set up mysql_length and such as construction- time arguments as is documented. I don't have anything else for that now unless you want to dig into DialectKWArgs and hack your value in for now when version 0.9.3 is detected.
I think if there's a setter interface of some kind coming I'll pin the package to depend on <0.9.0 for now. Unfortunately fixing it for real would require some investment from folk who are otherwise occupied at the moment (it's complicated). Again, thanks for the quick turnaround. -- Chris Dent http://burningchrome.com/ [...] -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
