if you can package up a script with full context that would help, that pullreq appears to add a new type to a file and I don't see how that results in anything happening.
In general if you are using my recipe earlier that features "ColumnElement", that object won't report on its parent "table" for usage in the FROM clause, if you are producing a custom column class you need to set it up correctly for the way it will be used. On Mar 24, 2013, at 3:43 PM, Tobias Bieniek <tobias.bien...@googlemail.com> wrote: > I've tried to extract the basic structure from this sample code and merge it > into the GeoAlchemy2 project, but somehow it fails to work for my specific > use-case: https://github.com/geoalchemy/geoalchemy2/pull/18 > > I'm trying something like: select([func.SomeFunction(table.c.some_column, > type_=mytype).attr1]) > > Unfortunately the resulting query string is missing the FROM clause and won't > execute. I'd be glad if anyone has an idea how to fix this. > > -- > 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 sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
