Scope functions and triggers to schema search path#168
Scope functions and triggers to schema search path#168teoljungberg merged 1 commit intoteoljungberg:masterfrom
Conversation
|
Looks great! I'll happily port this in. The test failure seems to have been a cosmic fluke. I'll do a release with this included soon. |
|
@teoljungberg Thanks! |
|
Hm, the tests are indeed flaky after this. See #169 as I'm trying to reproduce it without pushing more commits to master. Any ideas as to how to fix this @tylerhunt ? |
|
The specs seem to have been flaky to begin with. Running |
|
Huh, I have not run into this. I wonder what caused it. |
|
Hmm, I may be wrong about the randomization bit, since I see now that CI is using |
Hey @teoljungberg, any plan to release a new version soon? We are adding fx and having to monkey patch for this same reason. Thanks! |
|
@frank-west-iii - I can absolutely make that happen. Give me a few days. In the meantime you can point to a commit from master that gives you the unreleased features you need. |
Updates the function and trigger queries for PostgreSQL to only return objects from the current schema search path.
This is based on how Rails limits dumping objects like enums (rails/rails#47791).
Resolves #164.