thanks for the quick reply! > 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.
you are right, https://github.com/Turbo87/geoalchemy2/commit/9d09a94c97faab902ca29000c6e985a7b51f7eb1#L1R154is adding the PGCompositeType class, which is similar to the one in your recipe but with a few simplifications. https://github.com/Turbo87/geoalchemy2/commit/9d09a94c97faab902ca29000c6e985a7b51f7eb1#L0R220 is adding the corresponding unit test for that class, which is unfortunately failing at the moment, due to the missing FROM clause. you should be able to run the test case through "python setup.py nosetests". there will be a few failing functional tests due to the missing postgres DB, but the relevant test in "test_types.py" should be visible too. > 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. could you point me in the right direction how to "set it up correctly"? I'm currently a bit lost in the documentation and code. -- 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.
