hstore error about dataset HOT 5 CLOSED

This seems to be an issue in the underlying SQLAlchemy bindings. Officially, HSTORE support seems to have been added in 0.8, but that doesn't seem to work in your case?

Anyway, I'm not sure it's useful for us to start tracking SQLAlchemy issues on this bugtracker -- would you mind closing this and moving it over to them? If we need to update the SQLAlchemy version we run against, thats an easy thing to do, though.

from dataset.

Not sure it is entirely an SQLAlchemy bug. I am using the same versions of SQLA and psycopg2 with other programs and not seeing this problem. I will do some further digging before closing.

from dataset.

You where right it is a SQLA issue, fixed in 0.8.1 release.

from dataset.

So it'd be useful to up the dependency?

On Mon, Apr 29, 2013 at 10:46 PM, Adrian Klaver [email protected]:

You where right it is a SQLA issue, fixed in 0.8.1 release.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-17193196
.

from dataset.

Yes, if you are using hstore. In my case what confused me was that the table I was running datafreeze against did not actually contain an hstore column and the error was a no-op. Digging deeper, showed that the reflection process gathers information on all types registered in the database. In was in that procedure that the error was thrown not the fetching of data from the table.

from dataset.