Talk:Consistency (database systems)

report
what is a report in a database?

does anyone know —The preceding unsigned comment was added by 212.120.229.160 (talk)


 * If you were referring to this article then in that context, it refers to error reporting &mdash; e.g., letting the user/admin/whomever know that an error has occured. -- intgr 12:39, 27 February 2007 (UTC)

i wanna knw wat does consistecy actually means regarding the consistencyconsistency constraints????? —Preceding unsigned comment added by 115.115.37.11 (talk) 06:40, 29 August 2010 (UTC)

Inadequate explanation
The explanation in this article does not adequately explain the term, ie it uses other terms that are not explained. Eg what is an "illegal state"? An example would be very useful here. FreeFlow99 (talk) 12:25, 24 September 2013 (UTC)

Proposed merge with Data consistency
I've proposed the merge to this page for a few reasons: The above said, I haven't gone through with the merge myself as there may be distinctions between the two of which I'm not aware. Therefore, I figured the best thing to do would be to put it out there to see what the consensus is.
 * The naming convention is in line with other pages that treat the ACID transaction model (e.g. Atomicity (database systems));
 * The present article has fewer page issues than Data consistency;
 * The present article has more references than Data consistency.

As the nominator, I'll obviously start with a vote to Support the merge. — Sasuke Sarutobi (talk) 12:36, 11 November 2014 (UTC)
 * Database consistency is a special case of data consistency, with specifically defined conditions, and a large enough subsubject for a stand alone article. As such, I don't support the merge. Martijn Hoekstra (talk) 12:58, 11 November 2014 (UTC)


 * oppose Database consistency is one very narrow case of the overall data consistency landscape. It involves specific problems, that can be solved within the narrow scope of the database system. There are many other causes of inconsistency that just don't arise there, and where single-database solutions can't be applied to them. This would not be a good merge, for either article. Andy Dingley (talk) 15:27, 11 November 2014 (UTC)


 * neutral: at first, the merge seems reasonable to me, but I am a layman in this area and the comments of Martin and Andy are convincing. − Pintoch (talk) 21:17, 11 November 2014 (UTC)


 * Oppose - As points out, Database consistency is a specific case of the overall data consistency. I could see a merge of Consistency (database systems) into Data consistency working but not the proposed merge the opposite direction. ~KvnG 15:11, 14 November 2014 (UTC)
 * I wouldn't even merge that way - database consistency is a big enough topic to justify, and to benefit from, standing alone. Andy Dingley (talk) 15:17, 14 November 2014 (UTC)
 * I wouldn't propose such a merge but I might be persuaded by a charismatic editor to support it. ~KvnG 17:38, 14 November 2014 (UTC)


 * Oppose - Consistency in the realm of Databases is a guarantee that no matter the interleavings of concurrent modifications to the database, that the result of any modifying transaction will be visible concurrently to all nodes. That is, a modification will become visible to all parties attempting to access the database. The page that has been suggested to merge (Data_consistency)discusses the consistency of data in many different applications. Instead of merging the two sources, I would suggest a refinement of the content on Data_consistency to remove overlapping content. TimelyToga (talk) 18:05, 27 December 2016 (UTC)