CodedThought.Core.Data.SqlServer 10.0.1.4

CodedThought.Core.Data.SqlServer

A .NET Core Data Entity Provider for Sql Server.

Requirements

SqlServer requires CodedThough.Core.Configuration and CodedThought.Core. These can be found in NuGet. - CodedThought.Core.Configuration - CodedThought.Core

Usage

1. Install required packages. See requirements above.
2. Add the Database Connection settings in the appSetting.json or a custom .json file.

   Note: See CodedThought.Core.Configuration for JSON configguration specifications.

3. Add a new class and inherit from CodedThough.Core.Data.GenericDataStoreController. Below is a sample class file.

    using CodedThought.Core;
    using CodedThought.Core.Data;
    public class DataController : GenericDataStoreController {

		public DataController(IMemoryCache cache, CodedThought.Core.Configuration.ConnectionSetting	 connectionSetting	) {
			DataStore = new GenericDataStore(cache, connectionSetting, "dbo");
		}

		public Person GetPerson(string email)
		{
			try
			{
				ParameterCollection param = DataStore.CreateParameterCollection();
				param.AddStringParameter("EmailAddress", email);
				return DataStore.Get<Person>(param);
			} catch (Exception)
			{

				throw;
			}
		}
            
        public List<Person> GetPeople() {
            try {
                return DataStore.GetMultiple<Person>(null);
            } catch {
                throw;
            }
        }
    }
    using System.Data;
    using CodedThought.Core;
    using CodedThought.Core.Data;
	///<summary>
	/// Person class used by the framework to locate the right table and columns with class and proprety annotations.
	///</summary>
	[DataTable("tblPeople")]
	public class Person
	{
		public Person() { }
		[DataColumn("EmailAddress", DbType.String, DataColumnOptions.PrimaryKey)]
		public string EmailAddress { get; set; }
        [DataColumn("FirstName", DbType.String)]
		public string FirstName { get; set; }
		[DataColumn("LastName", DbType.String)]
		public string LastName { get; set; }
	}

Release Notes

10.0.1.4

Write Path Performance

Both paths in Add issue a single statement, and the identity path batches the INSERT with SELECT SCOPE_IDENTITY() into one command, so each was already atomic. The surrounding BEGIN TRANSACTION and COMMIT TRANSACTION added two network round trips without adding safety. Exception translation is unchanged.

Measured against a remote SQL Server where one round trip cost approximately 45.5 ms, averaged over interleaved A/B passes of 30 iterations:

Note: These figures are specific to a high-latency connection. The improvement is a reduction in round trips, so the benefit shrinks as server latency approaches zero. Reads were already efficient and are unchanged.

Remove and Update are not overridden by this provider, so their improvement comes from the matching change in CodedThought.Core 10.0.1.4. The Update gain depends on the Get fix above, because a read before a write used to commit the caller's transaction and force the following write to open a new one.

Upgrade Notes

Code that relied on Add or Get implicitly committing an open transaction must now commit explicitly.