On Monday, March 24, 2014 8:45:17 PM UTC-7, Tim Uckun wrote: > > Prepared transactions didn't work with redshift ( undefined method `[]' > for nil:NilClass). I am guessing this is because redshift doesn't support > prepared transactions. So I guess my only option is the > Sequel.transactions method. >
Undefined method for NilClass sounds like an error at the ruby level, not the database level, but I'd need to see the full backtrace to determine the cause. PostgreSQL doesn't support prepared transactions in the default configuration, you have to manually modify your postgresql.conf to support them. > Is there a way to turn off autocommit on the individual calls? > I'm not exactly sure what you mean. If you aren't inside a transaction, PostgreSQL treats each statement as inside it's own transaction. I'm guessing the answer to your question is to enclose the individual calls in a transaction block. 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/d/optout.
