Re:A database built like an operating system: the architectu...
by vbezhenar on Saturday April 01, 2017 @03:52AM
(#14011076)
NTFS definitely have transactions. I'm not sure about other file systems.
[ Parent
| on HN ]
Re:A database built like an operating system: the architectu...
by krylon on Saturday April 01, 2017 @04:52AM
(#14011257)
I had totally forgotten about that, you are right, NTFS does have a transaction API.
I think I remember the API being marked as deprecated, though. Or is my memory playing tricks on me again?
Re:A database built like an operating system: the architectu...
by vbezhenar on Saturday April 01, 2017 @06:03AM
(#14011421)
Yes, they deprecated it, claiming that developers didn't use it: https://msdn.microsoft.com/en-us/library/windows/desktop/hh8...
Re:A database built like an operating system: the architectu...
by skissane on Saturday April 01, 2017 @06:19AM
(#14011449)
IMO, part of why developers didn't use it was the API design made using it too painful. They took most of the existing file APIs and added new *Transacted APIs alongside them, e.g. CreateFile begot CreateFileTransacted, etc. So to add filesystem transactions to your existing code, you had to change all the file API calls.
I think, if they had made transactions work with the existing file API–such as by storing the hTransaction in thread-local storage, with an API to get/set the transaction association of the current thread, and having the existing non-transactional APIs behave transactionally in that case–it might have saw more adoption by developers.