Thanks! That seemed to do the trick. RedShift is based on Postgres 8.0.2, so I was warned that some things may not work... but so far so good.
On Tuesday, July 16, 2013 12:53:29 PM UTC-4, Jeremy Evans wrote: > > On Tuesday, July 16, 2013 9:32:16 AM UTC-7, David Kulp wrote: >> >> I'm experimenting with AWS' RedShift. Its interface is postgres. Pretty >> slick. > > > Apparently its interface isn't exactly postgres, since it doesn't handle > SET commands that PostgreSQL does. :) > > >> But their postgres variant doesn't respond to the "SET" commands that are >> issued during an initial Sequel connection. Specifically: >> >> > SET standard_conforming_strings = ON; >> ERROR: unrecognized configuration parameter "standard_conforming_strings" >> > SET client_min_messages = 'WARNING'; >> ERROR: permission denied to set parameter "client_min_messages" to >> "WARNING" >> >> I suspect that things will work OK if I remove these settings, but what's >> the best way to go about doing that? Are there Sequel parameters that >> allow me to inhibit these commands? Should I subclass the postgres adapter >> and override these settings? Recommendations welcome. >> > > You can use :client_min_messages => '', :force_standard_strings => false > options to not send those queries to the server. > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/groups/opt_out.
