On Wed, Jun 15, 2011 at 3:34 PM, Michael Bayer <[email protected]> wrote: > > On Jun 15, 2011, at 8:21 AM, Eric Lemoine wrote: > >> >> The function '_compiler_dispatch' just makes sure, that we are using >> the correct geometry type in the cast. >> ------ >> >>> have you tried subclassing UserDefinedType >>> instead ? >> >> Not yet. If you tell me that's what we should do I'll give it a try. > > yeah the point of UserDefinedType was so that people don't have to worry > about _compiler_dispatch details or forwards-compatibility - you just apply a > get_col_spec() method like in previous releases. > > http://www.sqlalchemy.org/docs/core/types.html#creating-new-types
Thanks. Here's my change: <https://bitbucket.org/geoalchemy/geoalchemy/changeset/509a36b0cabb>. Everything seems to be working correctly, although we haven't run the tests against MSSQL yet. -- Eric Lemoine Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac, Cedex Tel : 00 33 4 79 44 44 96 Mail : [email protected] http://www.camptocamp.com -- 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.
