This question is locked. New answers and comments are not allowed.
Hil All,
The scenario that I'm working with can best be compared to a source control system.
Where the workflow is like this:
The scenario that I'm working with can best be compared to a source control system.
Where the workflow is like this:
- user checks out data
- user works on the data (over days)
- user commits the changes (or drops them)
What would be best approach to solve this in OpenAccess ?
In an old-school database application one would just have created user associated tables as needed at runtime, something I don't think is the ORM way.
Yours
Björn
1 Answer, 1 is accepted
0
Hi Bjössi,
You could use Telerik OpenAccess ORM tocreate a new domain model and use it to execute CRUD operations against the database.
Additional information regarding Telerik OpenAccess ORM can be found here and here. Also you can have a look at our Product SDK, which contains a lot of examples for using OpenAccess as well as useful links and contents.
Hope that helps. If any other questions arise, please contact us back.
Greetings,
Damyan Bogoev
the Telerik team
You could use Telerik OpenAccess ORM tocreate a new domain model and use it to execute CRUD operations against the database.
Additional information regarding Telerik OpenAccess ORM can be found here and here. Also you can have a look at our Product SDK, which contains a lot of examples for using OpenAccess as well as useful links and contents.
Hope that helps. If any other questions arise, please contact us back.
Greetings,
Damyan Bogoev
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items