Posté par
L(page perso, ) le 28/09/2006 à 07:01. (lien). Évalué à 1.
Sortir un exemple de problème recherché à l'arrache sur Google pour dire que tel logiciel des limitations, c'est le degré zéro de l'argumentation. Tiens, je me suis amusé à faire pareil :
http://www.omnistarinc.com/~fonin/devtools.php : « Main PostgreSQL drawback is a large number of critical bugs in it. Once when I have a few PostgreSQL-driven applications the most part of my time was wasted to fix the problems produced by this database. PostgreSQL is claimed to be a transactional database, and this means that your data should be safe in the case of software crashes. It is still possible that you will loose your data with PostgreSQL, because of bugs in it. MySQL have no transactional support in its standard distribution (although it has transactional support with extended distribution called mysql-max). However I've never seen data loss with MySQL even with often power-offs, when the system was shut down uncleanly. PostgreSQL is an example of excellent idea and poor implementation. It has much more functions and tools than MySQL and had the transactional support from the start of its development. Moreover, PostgreSQL transaction concept is more powerful than MySQL one (multiversioning vs. table/page/row-level locking). Unfortunately all this cannot be regarded because of lack of reliability. Additionally, MySQL is much faster database and has better performance than PostgreSQL. That's why MySQL is more popular than its competitor. On the contrary, MySQL has attracted a huge number of users during its lifetime. It is very reliable. It gained a lot of functions that are associated with the commercial databases (transactional support, full-text search, replication). Most part of these functions are absent in the PostgreSQL. »
Re: Bonne nouvelle
Sortir un exemple de problème recherché à l'arrache sur Google pour dire que tel logiciel des limitations, c'est le degré zéro de l'argumentation. Tiens, je me suis amusé à faire pareil :
http://www.omnistarinc.com/~fonin/devtools.php : « Main PostgreSQL drawback is a large number of critical bugs in it. Once when I have a few PostgreSQL-driven applications the most part of my time was wasted to fix the problems produced by this database. PostgreSQL is claimed to be a transactional database, and this means that your data should be safe in the case of software crashes. It is still possible that you will loose your data with PostgreSQL, because of bugs in it. MySQL have no transactional support in its standard distribution (although it has transactional support with extended distribution called mysql-max). However I've never seen data loss with MySQL even with often power-offs, when the system was shut down uncleanly. PostgreSQL is an example of excellent idea and poor implementation. It has much more functions and tools than MySQL and had the transactional support from the start of its development. Moreover, PostgreSQL transaction concept is more powerful than MySQL one (multiversioning vs. table/page/row-level locking). Unfortunately all this cannot be regarded because of lack of reliability. Additionally, MySQL is much faster database and has better performance than PostgreSQL. That's why MySQL is more popular than its competitor. On the contrary, MySQL has attracted a huge number of users during its lifetime. It is very reliable. It gained a lot of functions that are associated with the commercial databases (transactional support, full-text search, replication). Most part of these functions are absent in the PostgreSQL. »
[ Répondre ]