Invalid column name 'Id'. Invalid column name 'id'.
Hello Friends,
I would like to develop a site with Umbraco.
I opened a project and created the project by adding Umbraco Cms Dll. Everything was going well. I have published my blog and wanted to publish the article named "My Blog Post".
Note: There is no version update I installed directly 8.2
Received an error from the server
An error occured
Invalid column name 'Id'. Invalid column name 'id'.
Exception Details
System.Data.SqlClient.SqlException: Invalid column name 'Id'. Invalid column name 'id'.
Sql kullanıcım sa and this user Dbowner
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
The problem is caused by "collation". If the SQL server uses TurkishCIAS, the problem occurs that [I] is not equal to [i] even though it is CI. If you use any LATIN CI collation, the problem disappears. Because, [i] [I] is equal.
In this case, an answer needs to come from the developers, the solution to this problem with a database that supports Turkish is to map or rename the column names as Case Sensitive in C# codes.
Invalid column name 'Id'. Invalid column name 'id'.
Hello Friends,
I would like to develop a site with Umbraco. I opened a project and created the project by adding Umbraco Cms Dll. Everything was going well. I have published my blog and wanted to publish the article named "My Blog Post".
Note: There is no version update I installed directly 8.2
Received an error from the server An error occured Invalid column name 'Id'. Invalid column name 'id'.
Exception Details System.Data.SqlClient.SqlException: Invalid column name 'Id'. Invalid column name 'id'.
Sql kullanıcım sa and this user Dbowner
I shared a screenshot.
I've detected the problem, but I can't find the solution. The mapping in the npoco system does not work.
For me, the problem was the table [UFUserFormSecurity] was missing the ID column.
This was the correct schema:
CREATE TABLE [dbo].[UFUserFormSecurity] ( [Id] [int] IDENTITY(1,1) NOT NULL, [User] nvarchar NOT NULL, [Form] [uniqueidentifier] NOT NULL, [HasAccess] [bit] NOT NULL, [AllowInEditor] [bit] NOT NULL, [SecurityType] [int] NOT NULL, CONSTRAINT [Id] PRIMARY KEY CLUSTERED ( [Id] ASC )WITH (PADINDEX = OFF, STATISTICSNORECOMPUTE = OFF, IGNOREDUPKEY = OFF, ALLOWROWLOCKS = ON, ALLOWPAGELOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO
Gökhan Öztürk, did you solve your problem? I have the same problem.
Hi,
I have the same problem in different aspect.
The problem is caused by "collation". If the SQL server uses TurkishCIAS, the problem occurs that [I] is not equal to [i] even though it is CI. If you use any LATIN CI collation, the problem disappears. Because, [i] [I] is equal.
In this case, an answer needs to come from the developers, the solution to this problem with a database that supports Turkish is to map or rename the column names as Case Sensitive in C# codes.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.