-
Notifications
You must be signed in to change notification settings - Fork 0
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
Cannot insert explicit value for identity column #800
Comments
Unfortunately you've uncovered a mistake here made when I was setting up the schema migrations for Forms 10. There's an incorrect setting on one of the columns - specifically There's no issue with migrations from Forms 9, but the incorrect column setting is in place for any new installs using 10.0.0 to 10.0.3. I've done some investigations this morning and it looks like this doesn't matter for SQLite databases, and can be worked around for SQL Server if we first issue a To resolve, I'm going to do the following.
If, like you, you have a new install, you can also remove the incorrect setting yourself. Unfortunately SQL Server doesn't provide an The script for applying this is as follows:
To summarise:
|
Thanks for the info and help Andy! |
Getting a database related exception when trying to handle group based permissions:
@AndyButland I'm pretty certain this is not based on the previous issue I reported, albeit they might be related I guess?
Or it's something you already have considered but I mistook your explanations.
Specifics
Using Umbraco.Cms version 10.0.1 and Umbraco.Forms version 10.0.2.
Fresh/new database install on Docker image
mcr.microsoft.com/azure-sql-edge:latest
Steps to reproduce
New Umbraco project by running
dotnet new umbraco
(after installing template for v10.0.1).Expected result
See and adjust group permissions
Actual result
Infinite loading in UI, error in backend from ajax request:
Cannot insert explicit value for identity column in table 'UFUserGroupSecurity' when IDENTITY_INSERT is set to OFF.
The text was updated successfully, but these errors were encountered: