Talk:Durability (database systems)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
WikiProject iconDatabases Stub‑class (inactive)
WikiProject iconThis article is within the scope of WikiProject Databases, a project which is currently considered to be inactive.
StubThis article has been rated as Stub-class on Wikipedia's content assessment scale.

A new extension[edit]

Hi, I extended the existing stub to a full article for the PhD-level course Wikipedia:GLAM/PoliMi/2023 of Politecnico di Milano. TarkusTheTediousTaciturn (talk) 09:31, 7 July 2023 (UTC)[reply]

General comment[edit]

I do not have any remark for this article. It is well structured and accessible with different levels of complexity by readers from different backgrounds. Gps1810 (talk) 13:48, 7 July 2023 (UTC)[reply]

Feedback[edit]

Very well written and exaustive article about a fundamental topic in database theory! Isawisa (talk) 14:04, 7 July 2023 (UTC)[reply]

Review[edit]

Hi, thanks for the article, it's very detailed. The article makes it possible for people has no background in this area to learn something quickly. I just made a little syntax modification. Hui Lin 22 (talk) 21:47, 7 July 2023 (UTC)[reply]

Observations and suggestions for improvements[edit]

The following observations and suggestions for improvements were collected, following an expert review of the article within the Science, Technology, Society and Wikipedia course at the Politecnico di Milano, in July 2023.

Correzioni necessarie:

Dove dice "In transaction-based systems, the mechanisms that assure durability are historically associated with the concept of reliability of systems," confonde la parte col tutto, l'affidabilità di un sistema è garantita dalla quattro proprietà acide di cui una è la durabilità (non il contrario).

Questo pezzo "In fact, thanks to serializability, they can be discerned from other transactions and, therefore, their changes are discarded.[3] In addition, it is relevant to consider that in-place changes, which overwrite old values without keeping any kind of history are discouraged.[1] There exist multiple approaches that keep track of the history of changes, such as timestamp-based solutions[5] or logging and locking.[1]" non ha senso scritto così.

Nella parte "In particular, the logging mechanism is called write-ahead log (WAL) and allows durability by buffering changes to the disk before they are synchronized from the main memory. " citano WAL come IL logging mechanism, ma è un possibile meccanismo, non IL meccanismo.

--Aandurro (talk) 11:05, 28 July 2023 (UTC)[reply]