On Tue, 2012-05-15 at 00:24 -0700, Kyle Schaffrick wrote:
> On Mon, Apr 30, 2012 at 8:52 AM, Adam Tauno Williams
> Sure, my original version was the attachment
> here: http://groups.google.com/group/sqlalchemy/msg/6f7284341ab69164
FYI, for anyone looking for hstore.py in the future I've put a c
On Mon, Apr 30, 2012 at 8:52 AM, Adam Tauno Williams wrote:
> On Sun, 2012-04-15 at 05:32 -0700, Kyle Schaffrick wrote:
> > Wow, a blast from the past! :)
>
> Yes.
>
> > Which version of SQLAlchemy does your new version work with? It's
> > great that you are now able to get rid of the HStoreCompa
On Sun, 2012-04-15 at 05:32 -0700, Kyle Schaffrick wrote:
> Wow, a blast from the past! :)
Yes.
> Which version of SQLAlchemy does your new version work with? It's
> great that you are now able to get rid of the HStoreComparator, that
> really makes it easier to use. The version of SQLA I was u
Wow, a blast from the past! :)
Which version of SQLAlchemy does your new version work with? It's great
that you are now able to get rid of the HStoreComparator, that really makes
it easier to use. The version of SQLA I was using 2 years ago when I wrote
it required the custom comparator to make th
Hey this is very nice, a few comments:
1. MutableType is probably going away in 0.8, and even the presence of it
causes the ORM to perform very poorly when objects use a MutableType. We have
sqlalchemy.ext.mutable now as the alternative.
2. was going to say something about HStoreColumn(HStoreE
Hi!
I am exploring your hstore.py for some days now. At first, i fixed an error
which occured when the hstore-field in the database was empty (see
attachment). At next i found out, that keys in the dictictionary, that
shall be written into the database must be strings and not unicode. Is this
