How to manage 2 DAO methods in a single transaction?
In an interview someone asked me : How do we manage 2 transactional/dao methods in a single transaction. Desired capabilities:
Is there a formula for this?
TL/DR: Any way to work out if known numbers between a known start and ending figure should be positive or negative numbers?
Logging to database: Log first or action first?
Long story short, I’m working on a web-based frontend that interacts with a database, and one of the functions is that every action on a particular table gets logged to keep a full history of all changes to that table.
What is the purpose of setting an isolation level for an INSERT INTO statement?
I want to better understand how isolation levels work, and here is my current understanding:
How to share transaction across multiple repositories in DDD?
We are trying the Domain Driven Development (DDD) while working on a project.
How to share transaction across multiple repositories in DDD?
We are trying the Domain Driven Development (DDD) while working on a project.
What happens if computer crashes after giving commit command
If we are updating a field in SQL and ALTER the row also. After giving the COMMIT command, the system is crashed.
Is there a theory for “transactional” sequences of failing and no-fail actions?
My question is about writing transaction-like functions that execute sequences of actions, some of which may fail. It is related to the general C++ principle “destructors can’t throw,” no-fail property, and maybe also with multi-phase transactions or exception safety. However, I’m thinking about it in language-neutral terms. My concern is with correctly designing error handling in C++ functions that must be reliable. I would like to know what the concepts below are called so that I can learn more about them.
Is there a theory for “transactional” sequences of failing and no-fail actions?
My question is about writing transaction-like functions that execute sequences of actions, some of which may fail. It is related to the general C++ principle “destructors can’t throw,” no-fail property, and maybe also with multi-phase transactions or exception safety. However, I’m thinking about it in language-neutral terms. My concern is with correctly designing error handling in C++ functions that must be reliable. I would like to know what the concepts below are called so that I can learn more about them.
Is there a theory for “transactional” sequences of failing and no-fail actions?
My question is about writing transaction-like functions that execute sequences of actions, some of which may fail. It is related to the general C++ principle “destructors can’t throw,” no-fail property, and maybe also with multi-phase transactions or exception safety. However, I’m thinking about it in language-neutral terms. My concern is with correctly designing error handling in C++ functions that must be reliable. I would like to know what the concepts below are called so that I can learn more about them.