Talk:Comparison of relational database management systems: Difference between revisions
Content deleted Content added
m Signing comment by 85.53.50.115 - "→Multiversion concurrency control: new section" |
→Transaction types support: Agreement that transaction breakdown is needed. |
||
Line 36:
This page definitely needs an overview of which transaction types the databases support. For many applications, it is important that you can start a transaction, make 100 select queries over a period of 10 minutes, and know that the first and last query will deliver the same result if they're identical, even if the database is being used and written to by other users in the same time period. It's needed because that's the only way you can make correct multi-query reports from production databases. For instance, Microsoft SQL Server 2000 doesn't support this. Also, it would be interesting to know what the default transaction type is - because that's typically the one that people use.[[Special:Contributions/87.63.152.70|87.63.152.70]] ([[User talk:87.63.152.70|talk]]) 06:48, 1 May 2008 (UTC)
: I don't see the point you're trying to make, but this sounds like ACID 'C' and there is a whole column for that, even if it's filled with random values apparently (...)[[User:Yourbane|Yourbane]] ([[User talk:Yourbane|talk]]) 10:24, 23 August 2011 (UTC)
: A agree that a section with a detailed ACID break-down is necessary. Pessimistic vs. optimistic concurrency, distributed transaction support, isolation level support, level of durability. This is one of the most difficult aspects of DBMS implementation and is one of the most important when comparing. --[[Special:Contributions/66.43.16.227|66.43.16.227]] ([[User talk:66.43.16.227|talk]]) 19:09, 15 November 2012 (UTC)
== Tables and views ==
|