On Tue, Feb 28, 2012 at 5:20 PM, Eric Lemoine <eric.lemo...@camptocamp.com> wrote: > On Tue, Feb 28, 2012 at 4:46 PM, Michael Bayer <mike...@zzzcomputing.com> > wrote: >> wow....well yeah, though putting it in the column_info is not how i'd want >> to do that. I'd like to change the API for 0.8. Actually the whole >> inspector should be passed to the event. this is >> http://www.sqlalchemy.org/trac/ticket/2418 which has a patch. >> >> For now, uerg, putting in the column_info is pretty hacky and then we're >> stuck with it....let me do some other things for a bit and if you have >> workarounds until 0.8 that would help, though I'm guessing you dont... > > Thanks for your answer. > > I have a workaround, but which forces me to have my reflection code at > the application level as opposed to in GeoAlchemy.
Another issue: GeoAlchemy defines a specific Column, namely GeometryColumn [*]. GeometryColumn is actually a function that returns a column property created with column_property. And I cannot make SQLAlchemy reflection code use GeometryColumn instead of Column. I may be asking too much. What do you think? Thanks. [*] <https://github.com/geoalchemy/geoalchemy/blob/master/geoalchemy/geometry.py#L163> -- Eric Lemoine Camptocamp France SAS Savoie Technolac, BP 352 73377 Le Bourget du Lac, Cedex Tel : 00 33 4 79 44 44 96 Mail : eric.lemo...@camptocamp.com 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 sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
