-
Notifications
You must be signed in to change notification settings - Fork 77
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
create all upsert functions in a dedicated schema so they can be dropped all at once #106
Comments
👍 my app has enough postgres magic in it that I need to use |
I created a “clean_upsert” task that runs before the structure is dumped,
which would probably help you for the time being :). If I remember on
Monday to post it I will.
…On Sun, Jan 6, 2019 at 07:22 Justin Searls ***@***.***> wrote:
👍 my app has enough postgres magic in it that I need to use structure.sql
instead of schema.rb for tracking changes, and the rather dense generated
upsert functions add quite a lot of churn. Would this help that?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#106 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AACNf7WLVjs2BG8WZhF31FLqmVpBh_9Zks5vAhTSgaJpZM4TLEGm>
.
|
@pnomolos if you're still willing, would love to see that code :) |
Thanks, I found that on this issue yesterday and got it to work. I still don't really understand what |
@mkaplan9 Normally the upsert functions are versioned (for example: "upsert_1_2"). This just removes that versioning and since it's checking against a regular expression it just removes all the functions called "upsert.*" |
Ah ok that makes sense. Thanks! |
for example, schema name "upsert_VERSION"
since we control the invocation of the function, we could always invoke it with the
upsert_VERSION
schema prefixThe text was updated successfully, but these errors were encountered: