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

Upgrade v14 RC2>RC3 thows TABLE ALTER COLUMN permission faile #16261

Open
enkelmedia opened this issue May 10, 2024 · 1 comment
Open

Upgrade v14 RC2>RC3 thows TABLE ALTER COLUMN permission faile #16261

enkelmedia opened this issue May 10, 2024 · 1 comment
Labels

Comments

@enkelmedia
Copy link
Contributor

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

v14 RC3, upgrading from RC2

Bug summary

Getting this error

The index 'IX_umbracoUserGroup2Permission_userGroupKey' is dependent on column 'permission'. ALTER TABLE ALTER COLUMN permission failed because one or more objects access this column

Workaround
Before running the upgrade:

DROP INDEX [umbracoUserGroup2Permission].IX_umbracoUserGroup2Permission_userGroupKey

When upgrade is finished:

CREATE NONCLUSTERED INDEX [IX_umbracoUserGroup2Permission_userGroupKey] ON [dbo].[umbracoUserGroup2Permission]([userGroupKey] ASC)

Specifics

No response

Steps to reproduce

Install RC2, then upgrade to RC3 using SQL Server.

Expected result / actual result

No response

Copy link

Hi there @enkelmedia!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant