Open tscloud opened 8 years ago
Multiple SQL operations can be grouped together and their success or failure be committed or rolled back as a whole. This would be done for 1) atomicity: the success of each operation is contingent upon the success of all others, a single atomic operation or 2) performance: one big I/O is more efficient than a bunch of little ones.
In use for WeatherHistory inserts (untested) but should be used elsewhere as well.
What the hell is a transaction boundary?