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
2.34.0-RC1 upgrade fails if Jethro has services for since-deleted congregations #940
Comments
The attached PR (pls ignore the first) resolves this by recreating the deleted congregations, so the services are no longer dangling and the foreign key constraint can be applied. |
Nice. Thanks.
…On Sun, 20 Aug 2023 at 1:54 am, Jeff Turner ***@***.***> wrote:
The attached PR <#941> (pls
ignore the first) resolves this by recreating the deleted congregations, so
the services are no longer dangling and the foreign key constraint can be
applied.
—
Reply to this email directly, view it on GitHub
<#940 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQI5LFHUWIRZZFZSFPGWETXWDOQHANCNFSM6AAAAAA3WUXR6I>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
tbar0970
added a commit
that referenced
this issue
Aug 23, 2023
#940 - recreate deleted congregations to keep the foreign key constraint happy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Attempting to upgrade my 2.33.0 Jethro to 2.34.0-RC1, I get an error running
upgrades/2023-upgrade-to-2.34.sql
:The relevant line of SQL is tightening up the schema, so congregations cannot be deleted if they have associated services (#834):
jethro-pmm/upgrades/2023-upgrade-to-2.34.sql
Lines 44 to 45 in c19e9ff
Our Jethro did once have 3 temporary congregations, and a number of associated services.
I'm all for tightening the schema, but then the upgrade SQL needs to deal with the current messy reality somehow.
The text was updated successfully, but these errors were encountered: