On Wed, Feb 29, 2012 at 4:52 PM, Michael Bayer <mike...@zzzcomputing.com> wrote: > Ok I'm assuming geometrycolumn doesn't go into a Table it gets stuck on a > declarative class, Table wouldn't accept it.
I think that's correct. We use GeometryExtensionColumn in a Table. GeometryExtensionColumn is a subclass of Column used in a @compiles decorator. See <https://github.com/geoalchemy/geoalchemy/blob/master/geoalchemy/geometry.py#L151>. > I would modify this using the declarative reflection recipe, which sets up >everything that gets sent to mapper(). Iterate through the reflected table >columns and generate the appropriate column_property() based on column type. i'll look into that. Thanks a lot! -- 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.
