not which ones enforce it using any possible combinations of settings and in even the rarest exception cases. The listing should say which databases SUPPORT ACID. I'm changing this to 'yes' with a footnote saying the same thing that is stated in the MySQL article, that ACID is supported only when using what is sometimes not the default storage engine. If the data constraints are not enforced in the transaction and it is possible to commit values outside those constraints, surely the system is not ACID compliant. that the transaction enforces the database is taken from one consistent state to another. I.e."violates the integrity clause".īy my understanding of ACID compliance this is a blatant breach of the Consistency / Integrity clause of ACID compliance - i.e. The footnote for the MySQL DBMS support of ACID transactions says that the software will in some cases accept values outside a range specified in the data definition. How can MySQL possibly be ACID compliant? Surely it should be marked as "No" under ACID What about adding a mention of the programming language(s) that each DBMS implementation uses? Programming languages of the implementations? 45 Puropse of "Database capabilities" table?.44 No "Fundamental Features" for Filemaker.41 Improve SAP HANA related technical details.39 Referential integrity MySQL and MariaDB.37 Why Oracle is marked as ACID compliant?.30 Please categorize by serverless/client-server/etc.22 "Free" licensed versions of proprietary products not handled well.21.1 Referential Integrity isn't the key.10 Database Specific Proprietary Index schemes.4 We need comparison about clustering capabilities.3 Someone needs to add information about FileMaker Pro.2 How can MySQL possibly be ACID compliant? Surely it should be marked as "No" under ACID.1 Programming languages of the implementations?.
0 kommentar(er)
