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.
Thanks, appreciate it
IS
--
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/-/DS7rJwgjjBcJ.
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.
