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

The umbracoUser table is using the primary key name PK_user instead of PK_umbracoUser #17302

Closed
pschwarzkopf opened this issue Oct 17, 2024 · 2 comments
Labels

Comments

@pschwarzkopf
Copy link

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

14.3.0

Bug summary

The table "umbracoUser" is using the primary key name "PK_user" instead of "PK_umbracoUser".

[PrimaryKeyColumn(Name = "PK_user")]

Other tables use a prefixed primary key (example: the table "umbracoUserGroup" is using the primary key name "PK_umbracoUserGroup").

Specifics

This caused an issue with an existing application (with a user table already existing), when adding Umbraco.

Steps to reproduce

Create a user table with the primary key name PK_User, then try to add Umbraco to the application.

Expected result / actual result

No response

Copy link

Hi there @pschwarzkopf!

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 🤖 🙂

@NguyenThuyLan
Copy link
Contributor

Hi @pschwarzkopf , thank you for reporting the issue.
I think you are not forced to use Umbraco in the same database as the rest of your application.
And you have another way to resolve it.
Editing key name could have many affects so we don't consider to fix it now.

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

2 participants