This question is locked. New answers and comments are not allowed.
Hi forum,
I'm developping a new application, by using the new way of working of OpenAccess.
I used forward mapping, which created the db from the entity diagram (rlinq) I defined.
I now have 2 questions, which I was able to answer to with the OpenAccess ORM classic version (the previous app i developped was with it):
- First, how can I handle manually the transactions? Within how the software architecture is defined, the transaction management is part of the logic: several unitary requests to be considered as a whole (atomicity), but executed within several data access classes (because of different area of concerns). Typically, i want to be able to: 1: open a transaction, 2: do something with my objects, 3: commit (or rollback) my transaction
- Second, my application has several threads. I cannot find much explainations on how to handle multithreaded applications when using rlinq. In the rlinq model, the show model settings / backend settings allow to define the transaction mode, a multithreaded context, and an isolation level. My wish is to allow only one thread to access the database at a time, which I was not able to achieve when I played with these options.
I have searched for several days, but cannot find any information on that 2 points. Can i still work with the "new" ORM, or should i get back to the classic version for my concerns?
Hope somebody can help,
Tx in advance,
Antoine.
I'm developping a new application, by using the new way of working of OpenAccess.
I used forward mapping, which created the db from the entity diagram (rlinq) I defined.
I now have 2 questions, which I was able to answer to with the OpenAccess ORM classic version (the previous app i developped was with it):
- First, how can I handle manually the transactions? Within how the software architecture is defined, the transaction management is part of the logic: several unitary requests to be considered as a whole (atomicity), but executed within several data access classes (because of different area of concerns). Typically, i want to be able to: 1: open a transaction, 2: do something with my objects, 3: commit (or rollback) my transaction
- Second, my application has several threads. I cannot find much explainations on how to handle multithreaded applications when using rlinq. In the rlinq model, the show model settings / backend settings allow to define the transaction mode, a multithreaded context, and an isolation level. My wish is to allow only one thread to access the database at a time, which I was not able to achieve when I played with these options.
I have searched for several days, but cannot find any information on that 2 points. Can i still work with the "new" ORM, or should i get back to the classic version for my concerns?
Hope somebody can help,
Tx in advance,
Antoine.