> > > Sequel is much more than just sending raw SQL commands... You should > replace most of these commands by Sequel equivalents, if you wish to have a > portable/reusable code. > > This is the first time I am trying Sequel. I usually use AR but this project is not a rails project so I thought I'd use something lighter weight. I am not that concerned about portable code because I am using redshift and it's a bit weird. It's kind of postgres compatible but not really. I found a sequel adapter for it but I am hand rolling all the SQL. I don't mind, I am one of those strange people who likes SQL :) I also make use of some postgres and redshift specific stuff so I kind of have to anyway.
> Back to your use case: my original suggestion would have been to split > into 2 transactions. > > Yet the last snippet from Jeremy is an eye-opener: if any of 2 > transactions on DB1 and DB2 fails, then it would rollback on both DB. Is > this what you need? > Yes that is what I need but redshift doesn't have prepared transactions so I have to use ordinary transactions. Jeremy has been very patient and Sequel is really an awesome toolkit but for this use case I might have to use something else. Either that or I write my own rollback code. -- 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.
