I'm new to this, but the hole framework is pretty awesome.
Working with the hole Linq to SQL stuff for years and you brought the updates I'm looking for so long.
So first huge props here.
Long story short:
I started with a new project, it is an .Net Core ASP.Net WebAPI which will access and store some stuff in a MS SQL Server.
I already google around and found this article which is quite old but nearly exactly what is happening here.
Im trying to insert a object into the DB. The DB is quite simple for now, some tables, the one im testing with has one Primary Key a GUID and some mandatory and optional fields. I tried to use the IdGenerate feature with GUID and then any of the sub options allowed. Autosync set to OnInsert.
Code: Select all
CREATE TABLE [dbo].[test_process] ( [Id] UNIQUEIDENTIFIER DEFAULT (newid()) NOT NULL, [operationKey] NVARCHAR (50) NOT NULL, [created] DATETIME NOT NULL, [entity] NVARCHAR (100) NOT NULL, [ordertype] NVARCHAR (50) NOT NULL, [status] NVARCHAR (50) NOT NULL, [started] DATETIME NULL, [finished] DATETIME NULL, [canceled] DATETIME NULL, [failed] DATETIME NULL, [result] NVARCHAR (50) NULL, PRIMARY KEY CLUSTERED ([Id] ASC), );
(Original in german: "Operandentypkollision: uniqueidentifier ist inkompatibel mit numeric")
I tried to put the default Value on DB site to "newid()" which works in the "original" Linq to SQL.
Submit works, the object gets pushed to the DB but the ID didn't get back. Did I missed something ?
I have some other projects working with mostly latest SQL Servers.
Hope you could bring some light into it.
PS: Im using LinqConnect 4.9.1878.0 (hopefully latest) and MS SQL Server 2017