Zongsoft.Data ORM Framework

注：该项目已归档，对应的替代版本请参考：https://github.com/Zongsoft/Framework/blob/master/Zongsoft.Data

The Zongsoft.Data is a GraphQL-style ORM(Object/Relational Mapping) data access framework.

Its design philosophy is to represent the data structure relationship in a declarative way and de-scripting (i.e. data access and navigation without writing any SQL or SQL-like syntax structure), making access to data easier, application code cleaner, and providing the best comprehensive price/performance ratio.

Features

Support for strict POCO/POJO objects without any annotation(Attribute) dependency;
Support for read and write separate data access;
Support various data operations of table inheritance;
Support mapping isolation of business modules and complete extension mechanism;
Data navigation, filtering, paging, grouping, aggregation operations, etc. without SQL scripts;
Universal intuition for object-oriented developers, easy to understand, out of the box;
Provide excellent overall cost performance and complete solutions;
Minimal implementation dependencies, usually only require ADO.NET and native ADO.NET drivers or less.

Drivers

Deriver	Project Path	State
MySQL	/drivers/mysql	Available
SQL Server	/drivers/mssql	Available
PostgreSQL	/drivers/postgres	Unimplemented
Oracle	/drivers/oracle	Unimplemented
InfluxDB	/drivers/influx	Planning
Elasticsearch	/drives/elastics	Planning

Tip: If you need unimplemented drivers or commercial technical support, please contact us.(zongsoft@qq.com)。

Environment

.NET Framework 4.6+
.NET Standard 2.0+

Download

Source code compilation

It is recommended to create a Zongsoft directory in the non-system partition of the hard disk and clone the items such as Guidelines, Zongsoft.CoreLibrary and Zongsoft.Data, etc. into this directory.

The data schema

The data schema is a DSL(Domain Specific Language) that describes the shape of the data to be query or write (Delete/Insert/Update/Upsert), The representation is somewhat like GraphQL but does not require to predefined. It is used to define the data fields to be fetched and written, scopes for cascading deletes, etc.

The schema argumment in the data access method is the data schema, and the ISchema interface is the parsed schema expression.

Schema Syntax

schema ::=
{
    * |
    ! |
    !identifier |
    identifier[paging][sorting]["{"schema [,...n]"}"]
} [,...n]

identifier ::= [_A-Za-z][_A-Za-z0-9]*
number ::= [0-9]+
pageIndex ::= number
pageSize ::= number

paging ::= ":"{
    *|
    pageIndex[/pageSize]
}

sorting ::=
"("
    {
        [~|!]identifier
    }[,...n]
")"

Schema Overview

Asterisk(*): Indicates that all simplex/scalar properties (without navigation/complex properties) are included, and must be explicitly specified if you want to include navigation properties.
Exclamation(!): for exclusion, a single exclamation mark indicates the exclusion of the previous definition, and Exclamation + Property indicate a property that excludes the specified name.

Note: The data schema will be further grammatically enhanced later, such as the qualification of navigation properties, the type specification of non-deterministic navigation properties, and so on.

Sample description

*, !CreatorId, !CreatedTime

Note: All simplex/scalar properties without CreatorId and CreatedTime properties.

*, Creator{*}

Note: All simplex/scalar properties and Creator complex property(all simplex properties of this complex property).

*, Creator{Name,FullName}

Note: All simplex/scalar properties and Creator complex property(Include only the Name and FullName properties of the navigation property).

*, Users{*}

Note: All simplex/scalar properties and Users complex property (one-to-many), The collection property has no sorting, no paging.

*, Users:1{*}

Note: All simplex/scalar properties and Users complex property (one-to-many), Paginate the results of this collection property (page 1 / page size is the default).

*, Users:1/20{*}

Note: All simplex/scalar properties and Users complex property (one-to-many), Paginate the results of this collection property (page 1 / 20 per page).

*, Users:1/20(Grade,~CreatedTime){*}

Note: All simplex/scalar properties and Users complex property (one-to-many), Sorting and paginate the results of this collection property (Grade ascending and CreatedTime descending, page 1 / 20 per page).

Mapping file

A data map file is an XML file with a .mapping extension that is metadata that defines the relationship of the entity structure. Do not write metadata in a large application in a mapping file. A mapping file should be defined separately for each business module to ensure the isolation of the module.

We provide the Zongsoft.Data.xsd XML Schema file, It makes it easy for you to handwrite mapping files and eliminate the chance of errors.

Enable XML IntelliSense for mapping files:

Method 1： Add new an XML file called "{module}.mapping" to the business module project(for example: Zongsoft.Security.mapping or Zongsoft.Community.mapping), open the mapping file and click "XML" -> "Architecture" menu item in the Visual Studio, in the pop-up dialog box, click the "Add" button in the upper right corner to find the Zongsoft.Data.xsd file.

Method 2： Copy Zongsoft.Data.xsd to the XML Shemas template directory in Visual Studio, for example:

Visual Studio 2019 (Enterprise Edition)
C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Xml\Schemas

Although some programmers are used to using tools to generate mapping files, we still recommend handwriting:

Data structure and relationship are undoubtedly the lowest level of infrastructure for any system. The database table structure is the concrete manifestation of this structure relationship. The mapping file is the "treasure map" about definition of the structural relationship between the upper layer entities and the lower tables.

The mapping file should be uniformly updated by the system architect or the module development leader. The settings of inherits, immutable, sortable, sequence and navigation properties in the mapping have a crucial impact on the development of the application layer. so care must be taken carefully.

Usages

All data operations are performed through the data access interface (located on the Zongsoft.Data.IDataAccess interface in the Zongsoft.CoreLibrary) and support the following data access operations:

int Count(...)
bool Exists(...)
long Increment(...) long Decrement(...)
IEnumerable<T> Execute<T>(...) object ExecuteScalar(...)
int Delete(...)
int Insert(...) int InsertMany(...)
int Update(...) int UpdateMany(...)
int Upsert(...) int UpsertMany(...)
IEnumerable<T> Select<T>(...)

Remind:

The following examples are based on the Zongsoft.Community open source project, which is a complete community forum .NET backend project. It is recommended that you read the database table structure design document of the project to understand the relevant data structure relationship before reading following samples.

Query operation

Basic query

Returns all scalar fields by default, which can be explicitly specified by the schema argument.
The result of the query is lazy loading, traversing the result set or calling Linq's ToList(), First() extension methods to trigger actual data access.

Note: Because the query is not paged by default, you should avoid using Linq's ToList(), ToArray() extension methods to load the result set into memory, so as to avoid unnecessary data access and wasted memory space.

// Gets the entities of all scalar fields of the specified criteria(lazy loading)
var threads = this.DataAccess.Select<Thread>(
    Condition.Equal("SiteId", this.User.SiteId) &
    Condition.Equal("Visible", true));

// Get a single entity with the specified criteria(only specific fields)
var forum = this.DataAccess.Select<Forum>(
    Condition.Equal("SiteId", this.User.SiteId) &
    Condition.Equal("ForumId", 100),
    "SiteId,ForumId,Name,Description,CoverPicturePath").FirstOrDefault();

Scalar value query

Querying the value of a scalar avoids returning unwanted fields and avoids the performance penalty of populate the entity, while also making the business code more concise.

Call description:

A generic parameter is specified as a type that returns a scalar value or a convertible type of a field;
Must explicitly specify the entity name of the query(by the method's name argument);
Must explicitly specify the property name of the returned(by the method's schema argument).

var email = this.DataAccess.Select<string>("UserProfile",
    Condition.Equal("UserId", this.User.UserId),
    "Email" //Explicitly specify only the value of the "Email" field by the schema argument, which is a string type
).FirstOrDefault();

/* Return a scalar value set(IEnumerable<int>) */
var counts = this.DataAccess.Select<int>("History",
    Condition.Equal("UserId", this.User.UserId),
    "Count" //Explicitly specify only the value of the "Count" field by the schema argument, which is an integer type
);

Multi-field query

Query the values of multiple fields, and support returning any entity type, including class, interface, structure, dynamic class(ExpandoObject), and dictionary.

struct UserToken
{
    public uint UserId;
    public string Name;
}

/*
 * Note: The schema argument of this method can be missing or empty, and the actual effect is the same.
 * Because the return fields of the query method defaults to the intersection of schema and the properties and fields of the returned entity type.
 */
var tokens = this.DataAccess.Select<UserToken>(
    "UserProfile",
    Condition.Equal("SiteId", this.User.SiteId),
    "UserId, Name"
);

/*
 * When the entity to be accessed is different from the generic parameter type,
 * The entity class(structure, interface) can be annotated with ModelAttribute to determine its mapped entity name.
 */
[Zongsoft.Data.Model("UserProfile")]
struct UserToken
{
    public uint UserId;
    public string Name;
}

// Because the returned entity class(structure, interface) is annotated with the mapped entity name, the name argument is missing, and the code can be simplified as follows:
var tokens = this.DataAccess.Select<UserToken>(
    Condition.Equal("SiteId", this.User.SiteId)
);

/*
 * 1)The return result type is specified as a dictionary by a generic parameter.
 * 2)Explicitly specify the returned fields via the schema argument. If this argument is missing or an asterisk(*), all fields are returned by default.
 */
var items = this.DataAccess.Select<IDictionary<string, object>>(
    "UserProfile",
    Condition.Equal("SiteId", this.User.SiteId) &
    Condition.GreaterThan("TotalThreads", 0),
    "UserId,Name,TotalThreads,TotalPosts");

foreach(var item in items)
{
    item.TryGetValue("UserId", out var userId); // true
    item.TryGetValue("Name", out var name);     // true
    item.TryGetValue("Avatar", out var avatar); // false
    item.TryGetValue("TotalThreads", out var totalThreads); // true
}

/*
 * The result type specified by the generic parameter is ExpandoObject, which is then accessed dynamically.
 */
var items = this.DataAccess.Select<System.Dynamic.ExpandoObject>("UserProfile");

foreach(dynamic item in items)
{
    Console.WriteLine(item.UserId); // OK
    Console.WriteLine(item.Name);   // OK
    Console.WriteLine(item.Fake);   // Compiled successfully, but runtime error
}

Paging query

Specify the paging argument in the Select method for paging queries. For details, see the Paging settings class.

// Define the paging settings for the query(page 2, 25 per page)
var paging = Paging.Page(2, 25);

var threads = this.DataAccess.Select<Thread>(
    Condition.Equal(nameof(Thread.SiteId), this.User.SiteId) &
    Condition.Equal(nameof(Thread.ForumId), 100),
    paging
);

/*
 * After the query method is called, the paging variable is the paging result:
 * paging.PageCount indicates the total number of pages that satisfy the condition
 * paging.TotalCount indicates the total number of records that satisfy the condition
 */

Sorting query

Specify the sortings argument in the Select method to sort the query. For details, please refer to the Sorting settings class.

var threads = this.DataAccess.Select<Thread>(
    Condition.Equal(nameof(Thread.SiteId), this.User.SiteId) &
    Condition.Equal(nameof(Thread.ForumId), 100),
    Paging.Disable, /* It is explicitly specified here to disable paging(you can also specify a paging setting) */
    Sorting.Descending("TotalViews"),   // 1.Descending for TotalViews
    Sorting.Descending("TotalReplies"), // 2.Descending for TotalReplies
    Sorting.Ascending("CreatedTime")    // 3.Ascending for CreatedTime
);

Navigation properties

The navigation(complex) property is explicitly specified by the schema argument, which supports one-to-one(zero), one-to-many navigation relationships, and supports nesting at any level. See the syntax description of the Schema for more details.

One-to-One

/*
 * 1) The structural relationship of the Thread entity's Post navigation property(associated to the Post entity) is one-to-one,
 *    that is, multiplicity="!" in the mapping file(.mapping), so its corresponding SQL association is INNER JOIN.
 *
 * 2) The structure relationship of the Thread entity's MostRecentPost navigation property(associated to the Post entity) is one-to-one/zero(the default value),
 *    that is, multiplicity="?" in the mapping file(.mapping), so its corresponding SQL association is LEFT JOIN.
 */
var thread = this.DataAccess.Select<Thread>(
    Condition.Equal("ThreadId", 100001),
    "*,Post{*},MostRecentPost{*}"
).FirstOrDefault();

One-to-Many

/*
 * 1) The forum group(ForumGroup) Forums navigation property structure is one-to-many,
 *    that is, multiplicity="*" in the mapping file(.mapping), the navigation property will correspond to a new SQL query statement.
 *
 * 2) Whether it's a "one-on-one" or "one-to-many" navigation property, they all support arbitrary nesting.
 *
 * Note: The asterisk(*) indicates all scalar(simplex) properties without any navigation properties,
 *       so the navigation properties must be explicitly specified.
 */
var groups = this.DataAccess.Select<ForumGroup>(
    Condition.Equal("SiteId", this.User.SiteId),
    "*,Forums{*, Moderators{*}, MostRecentThread{*, Creator{*}}}"
);

Navigation constraint

Especially in a one-to-many relationship, it is often necessary to conditionally constrain the result set of the navigation property, which is the navigation constraint.

There is a one-to-many relationship between the forum(Forum) and the forum members(ForumUser). The moderators(Moderator) is a subset of the forum members(ForumUser), then the structural relationship is Expressed by complexProperty/constraints in the data mapping file.

As shown in the following code, the Users navigation property of the Forum entity represents the full set of forum members, and the Moderators navigation property is a subset of the forum members, which are all associated with the ForumUser entity.

<entity name="Forum" table="Community_Forum">
	<key>
		<member name="SiteId" />
		<member name="ForumId" />
	</key>

	<property name="SiteId" type="uint" nullable="false" />
	<property name="ForumId" type="ushort" nullable="false" sequence="#SiteId" />
	<property name="GroupId" type="ushort" nullable="false" />
	<property name="Name" type="string" length="50" nullable="false" />

	<complexProperty name="Users" role="ForumUser" multiplicity="*" immutable="false">
		<link name="SiteId" role="SiteId" />
		<link name="ForumId" role="ForumId" />
	</complexProperty>

	<complexProperty name="Moderators" role="ForumUser:User" multiplicity="*">
		<link name="SiteId" role="SiteId" />
		<link name="ForumId" role="ForumId" />

		<!-- Constraints of navigation property -->
		<constraints>
			<constraint actor="Foreign" name="IsModerator" value="true" />
		</constraints>
	</complexProperty>
</entity>

<entity name="ForumUser" table="Community_ForumUser">
	<key>
		<member name="SiteId" />
		<member name="ForumId" />
		<member name="UserId" />
	</key>

	<property name="SiteId" type="uint" nullable="false" />
	<property name="ForumId" type="ushort" nullable="false" />
	<property name="UserId" type="uint" nullable="false" />
	<property name="Permission" type="byte" nullable="false" />
	<property name="IsModerator" type="bool" nullable="false" />

	<complexProperty name="User" role="UserProfile" multiplicity="!">
		<link name="UserId" role="UserId" />
	</complexProperty>
</entity>

Navigation springboard

Point to another navigation property in the associated entity, which usually needs to be filtered with the use of navigation constraints. Take the Moderators navigation(complex) property of the Forum entity in the above mapping file as an example:

Specify the colon syntax of the role attribute of the navigation(complex) property: the left side of the colon is the associated entity name, and the right side of the colon is the corresponding target navigation property.
Define the constraint constraint for this navigation(complex) property.

Note: Since the moderator is not restricted by the forum member's Permission field, the definition of the moderator's entity type is UserProfile will be more concise and easy to use(avoid the jump navigation through ForumUser.User), so set role attribute of the Moderators navigation property is "ForumUser:User" to express this requirement.

Take the above data mapping fragment as an example, and feel the difference between the Users and Moderators property types of the Forum class.

public abstract class Forum
{
    public abstract uint SiteId { get; set; }
    public abstract ushort ForumId { get; set; }
    public abstract ushort GroupId { get; set; }
    public abstract string Name { get; set; }

    public abstract IEnumerable<ForumUser> Users { get; set; }
    public abstract IEnumerable<UserProfile> Moderators { get; set; }
}

public struct ForumUser : IEquatable<ForumUser>
{
    public uint SiteId;
    public ushort ForumId;
    public uint UserId;
    public Permission Permission;
    public bool IsModerator;

    public Forum Forum;
    public UserProfile User;
}

var forum = this.DataAccess.Select<Forum>(
    Condition.Equal("SiteId", this.User.SiteId) &
    Condition.Equal("ForumId", 100),
    "*, Users{*}, Moderators{*, User{*}}"
).FirstOrDefault();

// The type of moderator variable is UserProfile.
foreach(var moderator in forum.Moderators)
{
    Console.Write(moderator.Name);
    Console.Write(moderator.Email);
    Console.Write(moderator.Avatar);
}

// The type of member variable is ForumUser.
foreach(var member in forum.Users)
{
    Console.Write(member.Permission);

    Console.Write(member.User.Name);
    Console.Write(member.User.Email);
    Console.Write(member.User.Avatar);
}

Group query

Grouping queries support aggregate functions for relational databases, and in the future it will add more statistical functions to the time series database.

struct ForumStatistic
{
    public uint SiteId;
    public ushort ForumId;
    public int TotalThreads;
    public int TotalViews;
    public int TotalPosts;
    public Forum Forum;
}

var statistics = this.DataAccess.Select<ForumStatistic>(
    "Thread",
    Grouping
        .Group("SiteId", "ForumId")
        .Count("*", "TotalThreads")
        .Sum("TotalViews")
        .Sum("TotalPosts"),
    Condition.Equal("SiteId", this.User.SiteId) &
    Condition.Equal("Visible", true),
    "Forum{Name}"
);

The above query method call will be roughly generated as the following SQL script:

SELECT
    tt.*,
    f.Name AS 'Forum.Name'
FROM
(
    SELECT
        t.SiteId,
        t.ForumId,
        COUNT(*) AS 'TotalThreads',
        SUM(t.TotalViews) AS 'TotalViews',
        SUM(t.TotalPosts) AS 'TotalPosts'
    FROM Thread AS t
    WHERE t.SiteId = @p1 AND
          t.Visible = @p3
    GROUP BY t.SiteId, t.ForumId
) AS tt
    LEFT JOIN Forum f ON
        tt.SiteId = f.SiteId AND
        tt.ForumId = f.ForumId;

Navigation condition

Conditional filtering of entities associated with navigation properties.

/*
 * The query condition description:
 * 1) The most valuable thread associated with the History table(Thread.IsValued=true), and
 * 2) The viewing time(first or last) is within the last 30 days.
 */
var histories = this.DataAccess.Select<History>(
    Condition.Equal("Thread.IsValued", true) & /* The navigation condition */
    (
        Condition.Between("FirstViewedTime", DateTime.Today.AddDays(-30), DateTime.Now) |
        Condition.Between("MostRecentViewedTime", DateTime.Today.AddDays(-30), DateTime.Now)
    )
);

The above query method call will be roughly generated as the following SQL script:

SELECT h.*
FROM History h
    LEFT JOIN Thread t ON
        t.ThreadId = h.ThreadId
WHERE t.IsValued = @p1 AND
    (
        h.FirstViewedTime BETWEEN @p2 AND @p3 OR
        h.MostRecentViewedTime BETWEEN @p4 AND @p5
    );

Subquery filtering

The conditional filtering of a one-to-many navigation property corresponds to a subquery of SQL, expressed using the Exists operator.

The following code indicates that the forum visibility is "Internal" or "Public" under the site to which the current user belongs. If the forum visibility is "Specified", then it is determined whether the current user is a moderator or has forum member permissions.

var forums = this.DataAccess.Select<Forum>(
    Condition.Equal("SiteId", this.User.SiteId) &
    Condition.In("Visibility", Visibility.Internal, Visibility.Public) |
    (
        Condition.Equal("Visibility", Visibility.Specified) &
        Condition.Exists("Users",
                          Condition.Equal("UserId", this.User.UserId) &
                          (
                              Condition.Equal("IsModerator", true) |
                              Condition.NotEqual("Permission", Permission.None)
                          )
                        )
    )
);

The above query method call will be roughly generated as the following SQL script:

SELECT t.*
FROM Forum t
WHERE
    t.SiteId = @p1 AND
    t.Visibility IN (@p2, @p3) OR
    (
        t.Visibility = @p4 AND
        EXISTS
        (
                SELECT u.SiteId, u.ForumId, u.UserId
                FROM ForumUser u
                WHERE u.SiteId = t.SiteId AND
                      u.ForumId = t.ForumId AND
                      u.UserId = @p5 AND
                      (
                          u.IsModerator = @p6 OR
                          u.Permission != @p7
                      )
        )
    );

Type conversion

When the database field type does not match the corresponding entity property type (cannot be converted directly), you need to introduce a type converter for custom conversion logic.

For example, the Tags field type of the Thread table is nvarchar, but the type of the Tags property of the Thread model class is a string array, so data read and write operations require custom conversion of these two types. For specific implementations, please refer to the TagsConverter class, and the Tags property definition of the Thread model class.

Delete operation

this.DataAccess.Delete<Post>(
    Condition.Equal("Visible", false) &
    Condition.Equal("Creator.Email", "zongsoft@qq.com")
);

The above delete method call will be roughly generated as the following SQL script:

DELETE t
FROM Post AS t
    LEFT JOIN UserProfile AS u ON
        t.CreatorId = u.UserId
WHERE t.Visible=0 AND
        u.Email='zongsoft@qq.com';

Cascade deletion

Support for deleting sub-table records associated with "one-to-one(zero)" or "one-to-many" navigation properties.

this.DataAccess.Delete<Post>(
    Condition.Equal("PostId", 100023),
    "Votes"
);

The above delete method call will be roughly generated as the following SQL script(SQL Server):

CREATE TABLE #TMP
(
    PostId bigint
);

/* Delete the master table and export the associated field values of the one-to-many navigation property to the temporary table */
DELETE FROM Post
OUTPUT DELETED.PostId INTO #TMP
WHERE PostId=@p1;

/* Delete dependent table records, with the condition that a subset of the master table has been deleted */
DELETE FROM PostVoting
WHERE PostId IN
(
    SELECT PostId FROM #TMP
);

Insert operation

this.DataAccess.Insert("Forum", new {
    SiteId = this.User.SiteId,
    GroupId = 100,
    Name = "xxxx"
});

Associated insertion

Support "one-to-one" or "one-to-many" navigation properties to be inserted at the same time.

var forum = Model.Build<Forum>();

forum.SiteId = this.User.SiteId;
forum.GroupId = 100;
forum.Name = "xxxx";

forum.Users = new ForumUser[]
{
    new ForumUser { UserId = 100, IsModerator = true },
    new ForumUser { UserId = 101, Permission = Permission.Read },
    new ForumUser { UserId = 102, Permission = Permission.Write }
};

this.DataAccess.Insert(forum, "*, Users{*}");

The above insert method call will be roughly generated as the following SQL script(MySQL):

/* The master table insert statement, only once */
INSERT INTO Forum (SiteId,ForumId,GroupId,Name,...) VALUES (@p1,@p2,@p3,@p4,...);

/* Subtable insert statement, multiple executions */
INSERT INTO ForumUser (SiteId,ForumId,UserId,Permission,IsModerator) VALUES (@p1,@p2,@p3,@p4,@p5);

Update operation

var user = Model.Build<UserProfile>();

user.UserId = 100;
user.Name = "Popeye";
user.FullName = "Popeye Zhong";
user.Gender = Gender.Male;

this.DataAccess.Update(user);

The above update method call will be roughly generated as the following SQL script:

/* Note: Unmodified properties will not be generated as SET clause */

UPDATE UserProfile SET
Name=@p1, FullName=@p2, Gender=@p3
WHERE UserId=@p4;

Anonymous class

The data written can be an anonymous class, dynamic class (ExpandoObject), dictionary (IDictionary, IDictionary<string, object>), and the like.

this.DataAccess.Update<UserProfile>(
    new {
        Name="Popeye",
        FullName="Popeye Zhong",
        Gender=Gender.Male,
    },
    Condition.Equal("UserId", 100)
);

Exclude fields

Explicitly specify fields, or exclude some fields.

/*
 * Explicitly specify only the Name, Gender fields by using the schema argument,
 * Other fields are not modified regardless of whether they have changed.
 */
this.DataAccess.Update<UserProfile>(
    user,
    "Name, Gender"
);

/*
 * All fields can be updated by specifying the schema argument, but the CreatorId and CreatedTime are excluded,
 * Even if the model object pointed to by the user variable contains and changes the values of these two properties, their SET clauses will not be generated.
 */
this.DataAccess.Update<UserProfile>(
    user,
    "*, !CreatorId, !CreatedTime"
);

Associated update

Supports "one-to-one" or "one-to-many" navigation properties to be written at the same time. For "one-to-many" navigation properties, it also ensures that the property value (collection type) is written in UPSERT mode.

public bool Approve(ulong threadId)
{
    var criteria =
        Condition.Equal(nameof(Thread.ThreadId), threadId) &
        Condition.Equal(nameof(Thread.Approved), false) &
        Condition.Equal(nameof(Thread.SiteId), this.User.SiteId) &
        Condition.Exists("Forum.Users",
            Condition.Equal(nameof(Forum.ForumUser.UserId), this.User.UserId) &
            Condition.Equal(nameof(Forum.ForumUser.IsModerator), true));

    return this.DataAccess.Update<Thread>(new
    {
        Approved = true,
        ApprovedTime = DateTime.Now,
        Post = new
        {
            Approved = true,
        }
    }, criteria, "*,Post{Approved}") > 0;
}

The above update method call will be roughly generated as the following SQL script(SQL Server):

CREATE TABLE #TMP
(
    PostId bigint NOT NULL
);

UPDATE T SET
    T.[Approved]=@p1,
    T.[ApprovedTime]=@p2
OUTPUT DELETED.PostId INTO #TMP
FROM [Community_Thread] AS T
    LEFT JOIN [Community_Forum] AS T1 ON /* Forum */
        T1.[SiteId]=T.[SiteId] AND
        T1.[ForumId]=T.[ForumId]
WHERE
    T.[ThreadId]=@p3 AND
    T.[Approved]=@p4 AND
    T.[SiteId]=@p5 AND EXISTS (
        SELECT [SiteId],[ForumId] FROM [Community_ForumUser]
        WHERE [SiteId]=T1.[SiteId] AND [ForumId]=T1.[ForumId] AND [UserId]=@p6 AND [IsModerator]=@p7
    );

UPDATE T SET
    T.[Approved]=@p1
FROM [Community_Post] AS T
WHERE EXISTS (
    SELECT [PostId]
    FROM #TMP
    WHERE [PostId]=T.[PostId]);

Upsert operation

The Upsert operation corresponds to a single primitive language in SQL, providing higher performance and consistency, and provides very simple syntax support for the application layer.

Modify the History table, When the record specifying the primary key value(ie UserId=100 and ThreadId=2001) exists, then increment the Count field value; otherwise, a new record is added, and the the Count field value is 1.

this.DataAccess.Upsert<History>(
    new {
        UserId = 100,
        ThreadId = 2001,
        Count = (Interval)1;
        MostRecentViewedTime = DateTime.Now,
    }
);

The above upsert method call will be roughly generated as the following SQL script:

/* MySQL syntax */
INSERT INTO History (UserId,ThreadId,Count,MostRecentViewedTime) VALUES (@p1,@p2,@p3,@p4)
ON DUPLICATE KEY UPDATE Count=Count + @p3, MostRecentViewedTime=@p4;

/* SQL syntax for SQL Server or other(PostgreSQL/Oracle) support for MERGE statement */
MERGE History AS target
USING (SELECT @p1,@p2,@p3,@p4) AS source (UserId,ThreadId,[Count],MostRecentViewedTime)
ON (target.UserId=source.UserId AND target.ThreadId=source.ThreadId)
WHEN MATCHED THEN
    UPDATE SET target.Count=target.Count+@p3, MostRecentViewedTime=@p4
WHEN NOT MATCHED THEN
    INSERT (UserId,ThreadId,Count,MostRecentViewedTime) VALUES (@p1,@p2,@p3,@p4);

Other

For more details(such as read-write separation, inheritance tables, data schema, mapping files, filters, validators, type conversions, data isolation), please consult the related documentation.

If you agree with our design philosophy(ideas), please pay attention to the(Watch & Fork) and Star(Like) this project.

Performance

We want to provide the best overall price/performance ratio and not compromise our design goals for some of benchmarking. We believe that for an ORM data access engine, performance concerns are mainly(unlimited) with these elements:

Generate clean and efficient SQL scripts and make the best use of the latest SQL syntax of the specified database;
The model/entity populate process of the data query results must be efficient;
Avoid reflections, a valid syntax tree cache.

Thanks to the semantic design concept of “declaratively expressing data structure relationships”, compared with the imperative programming design, the program intention is more focused, and it is natural easier to convert the semantics into a syntax tree to represent SQL scripts of different data providers, and the optimization space of each step is more relaxed and free.

The implementation layer uses emitting dynamic compilation technology to pre-heat the model/entity populated, data parameter binding, etc., which can be understood by the DataPopulator class and related classes.

Contributing

Please do not submit a Question and Discussion in the Issues of the project. Issues are used to report bugs and features. If you wish to participate in the contribution, you are welcome to submit a code merge request(PullRequest) or an issue.

For new features, be sure to create a functional feedback(Issue) to describe your recommendations in detail so that we can fully discuss them, which will also allow us to better coordinate our work to prevent duplication of development and help you adjust recommendations or requirements to make it successfully accepted into the project.

You are welcome to write articles for our open source projects to promote, if you need to forward your Articles, Blogs, Videos, etc. on the official website(http://zongsoft.com/blog), you can contact us by email.

If you're new to posting issues, we ask that you read "How To Ask Questions The Smart Way", "How to Ask a Question in Open Source Community" and "How to Report Bugs Effectively" prior to posting. Well written bug reports help us help you!

Sponsorship

We look forward to your support and sponsorship. You can provide us with the necessary financial support in the following ways:

Follow the Zongsoft WeChat public account and reward our articles;
Join the Zongsoft Knowledge Planet to get online Q&A and technical support;
If your organization requires on-site technical support and coaching, or if you need some new features, instant bug fixes, etc., please contact us by email.

License

Licensed under the LGPL license.

Name		Name	Last commit message	Last commit date
Latest commit History 481 Commits
docs		docs
drivers		drivers
samples/benchmark		samples/benchmark
src		src
tests		tests
.deploy		.deploy
.gitignore		.gitignore
LICENSE		LICENSE
README-zh_CN.md		README-zh_CN.md
README.md		README.md
Zongsoft.Data.xsd		Zongsoft.Data.xsd

License

Zongsoft/Zongsoft.Data

Folders and files

Latest commit

History

Repository files navigation

Zongsoft.Data ORM Framework

注：该项目已归档，对应的替代版本请参考：https://github.com/Zongsoft/Framework/blob/master/Zongsoft.Data

Features

Drivers

Environment

Download

Source code compilation

The data schema

Schema Syntax

Schema Overview

Sample description

Mapping file

Usages

Query operation

Basic query

Scalar value query

Multi-field query

Paging query

Sorting query

Navigation properties

One-to-One

One-to-Many

Navigation constraint

Navigation springboard

Group query

Navigation condition

Subquery filtering

Type conversion

Delete operation

Cascade deletion

Insert operation

Associated insertion

Update operation

Anonymous class

Exclude fields

Associated update

Upsert operation

Other

Performance

Contributing

Sponsorship

License

About

Topics

Resources

License

Stars

Watchers

Forks

Releases

Packages 0

Contributors 2

Languages

Packages