Talk:Transaction log
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
| ||||||||
- TODO: Log Iteration and Interactions —The preceding unsigned comment was added by 212.97.178.235 (talk • contribs) 20:44, 6 August 2005 (EEST).
Too technical
[edit]The description of log attributes/data structures seems too technical for Wikipedia and fails to be informative for the casual reader, not to mention that different DBMSes probably implement logging differently. Does anyone think it should be rewritten? (No, I'm not volunteering ;) -- intgr 10:40, 30 June 2006 (UTC)
Rename to "transaction log"
[edit]I'm renaming this article from "database log" to "transaction log" since that's probably the least ambiguous way of referring to the concept. A "database log" can also be confused with a textual log file produced by a RDMS and "binary log" does not obviously say what the logs contain. "transaction log" also gets the most Google hits: "database log" (188,000), "binary log" (148,000) "transaction log" (952,000). -- intgr 16:51, 17 August 2006 (UTC)
Article is too low-level; needs rewrite
[edit]As it's written now, this article seems to be a low-level description of ARIES's data structures. This article should be re-written to discuss transaction logs in general. For example, not all logging schemes use both undo and redo logs, and not all schemes use CLRs. Similarly, the article could discuss logical vs. physical operation logging as a dimension of the logging design space.