On Thursday, September 27, 2012 2:55:07 PM UTC-7, Edward Muller wrote:
>
> We're trying to switch to native hstore support from our older, home grown 
> one.
>
> There is a place where we store some configuration files / scripts as 
> hstore values.
>
> When updating one of these values we came across a potential escaping 
> issue where the code generated SQL that produced a SYNTAX ERROR.
>
> The basic gist of this is ...
>
> UPDATE "something" SET thing = '"file" => ".....fooo \\"something\\"...."';
>
> causes a 'Syntax Error near 's' at position ...
>
> Simply adding an 'E" to the beginning of the value fixes things.
>
> This is with a psql 9.0 and 9.1 db and seems to make sense from what I've 
> read about standard_conforming_strings.
>
> Thoughts?
>

We definitely don't want to use escape strings.   See my reply at 
https://github.com/jeremyevans/sequel/pull/559.

Just to update everyone, Edward and I will be doing some testing to see if 
Sequel is actually literalizing the hstores incorrectly, or if there is 
some other issue causing his problem.

Thanks,
Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/sequel-talk/-/OETIeKZdM-oJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sequel-talk?hl=en.

Reply via email to