Postgres will now properly create hstore columns as it should, text is not a suitable alternative. This also fixes a describeTable issue with returning the column's data type as USER-DEFINED instead of HSTORE which closes #671
Merge pull request #816 from durango/hstore-describe

Postgres will now properly create hstore columns as it should, text is n...