On Thursday, December 6, 2012 8:31:55 PM UTC-8, CaduceusAbode wrote: > Hi all, > > I am encountering something that I found very strange with Sequel. I am > using a Postgres DB. > > I have a few "AFTER INSERT" triggers for a specific table. An "AFTER > INSERT" trigger could be something simple like this : > > CREATE TRIGGER after_insert_trigger AFTER INSERT ON theTable > > FOR EACH ROW > > EXECUTE PROCEDURE do_after_insert_trigger(); > > > When I do an INSERT from the Sequel side in Ruby( it could be using DB.run > , DB <<< or the add_* functions) and the "AFTER INSERT" triggers will not > trigger at all. > > But if I were to run the same exact INSERT query on the Postgres command > line directly, all the triggers work properly. I looked at the Postgres > logs and the queries look exactly the same coming from both Sequel and the > command line. > > I was wondering if there is something I missed in my Sequel config. This > only started happening very recently, and I do not recall changing anything > major > > I was hoping if anyone might be able to shed some light on this matter. >
The likelihood that this is a Sequel issue is very low. If you have a trigger defined in PostgreSQL, it should run no matter what program your are using to execute the query. Sequel doesn't do anything specific to disable triggers. If you think this issue is actually caused by something in Sequel, please include a self contained example showing the problem so we can test it. 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/-/pkUZaPVxMRAJ. 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.
