Dialect Refactor, Take II

We will need to make a much stronger separation between DBAPI, Dialect and Compiler in the near future. Systems like mxODBC and JDBC with Jython, both of which can talk to virtually every database we already support, present the need to have very different interaction between DBAPI behavior and SQL behavior.

The separation will place Compiler on one side of the coin, as well as the strings returned by TypeEngine; however the convert_bind_param()/convert_result_value() portions of types may need to be more on the DBAPI side (like maybe in ~~#526~~). Dialect will likely need to be split up and also allow a strategy pattern so that "crossover" elements may be shared between both sides.

Comments (8)