[OpenSIPS-Devel] [NEW] Virtual DB module

[Thomas Gelf]

Dan Pascu wrote:
> On Thursday 30 July 2009, Razvan Pistolea wrote:
> How does this work with operations that are separate, but still represent a 
> single logical operation, like for example writing usrloc, or dialog data into 
> the database not in real time but on a timer, where multiple records are 
> inserted at a time. If a connection fails in the middle of an operation, some 
> records will end up in one database and some in another and OpenSIPS will have 
> troubles finding the information later. Without having transaction support for 
> such operations, so that all the inserts that belong together fail and are 
> retried together on the next connection, it would be problematic.

I agree that transaction support would be not only a good idea, I
consider it really important - and probably not that hard to add (ok,
this depends strongly on how all these backends ar abstracted - it could
also be really tricky...).

> Another issue is that even if transaction support would be implemented, there 
> is still an uncertainty where the data is. If my usrloc or dialog data was 
> saved over multiple connections, after a restart, from where is OpenSIPS 
> supposed to read the data?