On Sep 11, 2010, at 11:26 PM, Simon Wittber wrote:
On Sep 12, 12:46 am, Michael Bayer mike...@zzzcomputing.com wrote:
OK, sure. beyond that though do queries with the column and such do whats
expected?
Just tried this morning, and it works as expected, create / update
statements
*shrugs* it might be tricky ensuring that return types for all those
operations are adequate, though that might not be necessary assuming psycopg2
does what the end user wants here.
My main problem is that table reflection returns the point type as a
NullType, and my code needs to know
On Sep 11, 2010, at 11:37 AM, Simon Wittber wrote:
its likely since psycopg2 is a pretty complete implementation. that's not
to say there arent advantages to having them on your table metadata, though.
what are you observing ?
When using inspect.get_columns(table_name), I receive this
On Sep 12, 12:46 am, Michael Bayer mike...@zzzcomputing.com wrote:
OK, sure. beyond that though do queries with the column and such do whats
expected?
Just tried this morning, and it works as expected, create / update
statements work fine. It seems psycopg2 takes care of everything.
-Sw.
