OneData 0.2.0.26-alpha

• .NETFramework 4.6.1

  • FastMember (>= 1.5.0)
  • Microsoft.CSharp (>= 4.5.0)
  • Microsoft.Extensions.Configuration (>= 2.1.1)
  • Microsoft.Extensions.Configuration.FileExtensions (>= 2.1.1)
  • Microsoft.Extensions.Configuration.Json (>= 2.1.1)
  • MySql.Data (>= 8.0.16)
  • Newtonsoft.Json (>= 12.0.2)
  • NLog (>= 4.6.3)
  • System.Configuration.ConfigurationManager (>= 4.5.0)
  • System.Data.Common (>= 4.3.0)
  • System.Data.DataSetExtensions (>= 4.5.0)
  • System.Data.SqlClient (>= 4.6.0)

• .NETStandard 2.0

  • FastMember (>= 1.5.0)
  • Microsoft.CSharp (>= 4.5.0)
  • Microsoft.Extensions.Configuration (>= 2.1.1)
  • Microsoft.Extensions.Configuration.FileExtensions (>= 2.1.1)
  • Microsoft.Extensions.Configuration.Json (>= 2.1.1)
  • MySql.Data (>= 8.0.16)
  • Newtonsoft.Json (>= 12.0.2)
  • NLog (>= 4.6.3)
  • System.Configuration.ConfigurationManager (>= 4.5.0)
  • System.Data.Common (>= 4.3.0)
  • System.Data.DataSetExtensions (>= 4.5.0)
  • System.Data.SqlClient (>= 4.6.0)

• .NETStandard 2.1

  • FastMember (>= 1.5.0)
  • Microsoft.CSharp (>= 4.5.0)
  • Microsoft.Extensions.Configuration (>= 2.1.1)
  • Microsoft.Extensions.Configuration.FileExtensions (>= 2.1.1)
  • Microsoft.Extensions.Configuration.Json (>= 2.1.1)
  • MySql.Data (>= 8.0.16)
  • Newtonsoft.Json (>= 12.0.2)
  • NLog (>= 4.6.3)
  • System.Configuration.ConfigurationManager (>= 4.5.0)
  • System.Data.Common (>= 4.3.0)
  • System.Data.DataSetExtensions (>= 4.5.0)
  • System.Data.SqlClient (>= 4.6.0)

Cope<T> class is no longer required by OneData.

With this, came the following breaking changes which is why the development was moved to a new branch:

- Class no longer need to inherit from Cope.
- Select statements have also been affected. To perform a select, instead of using the class name as before, you will need to instantiate an objecto of the desired type and then you will be presented with Select extensions.
- For compatibility reasons, class Cope was replaced with Extend and it is now optional, but if used, it helps easing querys and setting up compatible classes. You can choose to directly inherit from it or set your highest level class to inherit from it.

IManageable interface has been updated. Instead of holding a ModelComposition property, it now holds a GetComposition method that needs to be implemented using the following code block inside each class with their corresponding class type instead of T:

return Manager<T>.Composition;

With this change, OneData returns to its optimization state which was compromised yesterday by calling new T() everytime we needed access to a model composition.

Manager<T> is now not only holding the cached data but it's corresponding model composition with a static get-only property.