On Jun 26, 2013, at 11:22 AM, Michael Bayer wrote:
>
>
>
> OK just trying to get my head around the issue - psycopg2's parser does not
> have the backslashing issue right ?
psycopg2's parser is fine. the fix is committed in master / rel_0_8 branch,
thanks for the patch !
--
You receive
On Jun 26, 2013, at 6:57 AM, Ryan Kelly wrote:
> On Tue, Jun 06/25/13, 2013 at 02:47:18PM -0400, Michael Bayer wrote:
>>
>> On Jun 25, 2013, at 2:13 PM, Ryan Kelly wrote:
>>
>>> There are also some other parsing problems that I consider to be corner
>>> cases and broken as implemented in Post
On Tue, Jun 06/25/13, 2013 at 02:47:18PM -0400, Michael Bayer wrote:
>
> On Jun 25, 2013, at 2:13 PM, Ryan Kelly wrote:
>
> > There are also some other parsing problems that I consider to be corner
> > cases and broken as implemented in PostgreSQL, such as:
> >
> > (postgres@[local]:5432 14:05:4
On Jun 25, 2013, at 2:13 PM, Ryan Kelly wrote:
> As we're trying to convert from our own homegrown version of the HSTORE
> type, it seems that our tests have been broken by SQLAlchemy's handling
> of serialization/de-serialization for hstores containing backslashes.
>
> The current serializatio
As we're trying to convert from our own homegrown version of the HSTORE
type, it seems that our tests have been broken by SQLAlchemy's handling
of serialization/de-serialization for hstores containing backslashes.
The current serialization behavior of SQLAlchemy will do this:
{'\\"a': '\\"1'} => '
