Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nowrap option for PostgreSQL #31

Merged
merged 4 commits into from
May 21, 2014
Merged

Conversation

akamike
Copy link
Contributor

@akamike akamike commented May 15, 2014

Encountered a use case where I needed to execute an existing trigger (tsvector_update_trigger) but this was not compatible with how the PostgreSQL triggers are declared, as others have found. This nowrap chainable method sets an option to indicate that the raw_action should be executed directly, rather than being wrapped in a CREATE FUNCTION.

Wrapping the raw_action only seems to happen to PostgreSQL, and it looks like this was to enable security and legacy support for where. I have added appropriate warnings for when these options are set in conjunction with nowrap.

@jenseng
Copy link
Owner

jenseng commented May 15, 2014

From a quick glance, this looks great. I'll dig into it some more later and merge it in (or let you know if any tweaks are needed). Thanks! 👍

jenseng added a commit that referenced this pull request May 21, 2014
@jenseng jenseng merged commit 2a09a45 into jenseng:master May 21, 2014
@akamike akamike deleted the postgresql_nowrap branch May 21, 2014 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants