-
Notifications
You must be signed in to change notification settings - Fork 132
Enhancement: Complete support to the Fluent named-based operation #499
Copy link
Copy link
Closed
Labels
deployedFeature or bug is deployed at the current releaseFeature or bug is deployed at the current releaseenhancementNew feature or requestNew feature or requestfeatureDefined as a big development item (feature)Defined as a big development item (feature)fixedThe bug, issue, incident has been fixed.The bug, issue, incident has been fixed.priorityTop priority feature or things to doTop priority feature or things to dorequestA request from the community.A request from the community.todoThings to be done in the futureThings to be done in the future
Metadata
Metadata
Assignees
Labels
deployedFeature or bug is deployed at the current releaseFeature or bug is deployed at the current releaseenhancementNew feature or requestNew feature or requestfeatureDefined as a big development item (feature)Defined as a big development item (feature)fixedThe bug, issue, incident has been fixed.The bug, issue, incident has been fixed.priorityTop priority feature or things to doTop priority feature or things to dorequestA request from the community.A request from the community.todoThings to be done in the futureThings to be done in the future
RepoDb promises to be the hybrid ORM for .NET. Even though RepoDb supports both Dynamic and Fluent operations, but currently, RepoDb fluent implementation seems to be limited to an Entity Model.
This story would allow the library consumer to use the model (or a DataEntity class) to any table from the database. The intention is, if you have a table with an identical columns with other tables, then you can utilize single model for that.
See the sample code below.
Let us say, you have a Person like below.
And a Customer table like below.
Then, you create a class below.
Query
You should be able to query it like below. See the code for the Person table.
And Customer table.
Insert
You should be able to insert it like below. See the code for the Person table.
And Customer table.
Merge
You should be able to merge it like below. See the code for the Person table.
And Customer table.
Update
You should be able to merge it like below. See the code for the Person table.
And Customer table.
Extent (EDIT)
The extent of the changes must be on all operations available in RepoDb library.