I thought it might be worthwhile to sum up the various points about databases and zope and linux that were made today. Please correct any mistakes and provide any comments you have. - Zope has strong database connections for Oracle and Solid, with DB2 in the works. These are all officially supported DA's. - There is an ODBC DA, but it works only on Windows because there isn't a good ODBC implementation on Linux. This isn't Zope's fault. - There are DA's for MySQL and PostgreSQL, the two open source databases (yeah, yeah, MySQL isn't truly open source--although one of the older version is). They work, although both are still in development (is this active?) and some people have had troubles getting them to compile. This seems especially true of the MySQL DA judging from pleas for help sent to the zope list, although this may be more of a reflection of MySQL's popularity over PostgreSQL. - The big criticism against MySQL is the lack of transaction support. MySQL is not popular with the DC folks because of this. Their customers use DB's with transaction support (Oracle, Sybase, and DB2) and their main concern is developing and supporting DA's for DB's their clients use. - DC is looking for someone in the zope community to take ownership of the MySQL DA (what's the status of the PostgreSQL DA?) - Despite it's lack of transaction support, it was agreed that MySQL (a) is popular (b) is very fast and a good choice for sites that do high volume queries, but relatively simple and low-volume updates (c) will be getting transaction support "real soon now" according to the web site (d) should have a good, up to date, Zope DA - PostgreSQL, the other open source DB, does support transactions. There is a Zope DA. Some people suggested that PostgreSQL is a bit buggy. Other said that it works great. Everyone agreed that it's a bit on the slow side, especially when compared to MySQL. What am I missing? What did I get wrong? ----------------------------------------------------------------- Karl Fast
Karl Fast wrote:
I thought it might be worthwhile to sum up the various points about databases and zope and linux that were made today. Please correct any mistakes and provide any comments you have.
...
- Despite it's lack of transaction support, it was agreed that MySQL (a) is popular (b) is very fast and a good choice for sites that do high volume queries, but relatively simple and low-volume updates (c) will be getting transaction support "real soon now" according to the web site (d) should have a good, up to date, Zope DA
- PostgreSQL, the other open source DB, does support transactions. There is a Zope DA. Some people suggested that PostgreSQL is a bit buggy. Other said that it works great. Everyone agreed that it's a bit on the slow side, especially when compared to MySQL.
It is my understanding that even Oracle is "a bit on the slow side" when compared to MySQL, as are all other "real" DBMS's (ie transaction support, triggers, rules, user-defined functions, cost-based optimisation, extensible type system, etc...) OTOH, the slowness quickly diminishes when queries become more complex, even to the point where MySQL is slower And yes, PostgreSQL is a bit buggy _and_ it works great ;-p , i.e. there are some known bugs, (at least known to me) but it does really work great. ----------------- Hannu
At 06:31 PM 11/9/99 -0600, Karl Fast wrote:
- Despite it's lack of transaction support, it was agreed that MySQL (a) is popular (b) is very fast and a good choice for sites that do high volume queries, but relatively simple and low-volume updates (c) will be getting transaction support "real soon now" according to the web site (d) should have a good, up to date, Zope DA
Could anyone point out where the "real soon now" is on the site? Every time I've ever looked at the site it has said that they have no plans to implement fully ACID transactions, ever.
"Phillip J. Eby" wrote:
At 06:31 PM 11/9/99 -0600, Karl Fast wrote:
- Despite it's lack of transaction support, it was agreed that MySQL (a) is popular (b) is very fast and a good choice for sites that do high volume queries, but relatively simple and low-volume updates (c) will be getting transaction support "real soon now" according to the web site (d) should have a good, up to date, Zope DA
Could anyone point out where the "real soon now" is on the site? Every time I've ever looked at the site it has said that they have no plans to implement fully ACID transactions, ever.
The "real soon now" has been deduced from the fact that transactions are the top item ( or second top item ) on their tondo list. The assumption is that's the next thing they will do. This assumption has somehow diffused into the folk awareness and has become "truth". I have not seen any confirmation of this assumption from the MySQL folks. Nitin Borwankar
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
I started a reply to this thread on the Zope list, then went of on a tangent about Zope PostgreSQL synergies, so I moved my reply over to the zope-dev list. A brief reply as to the PyGreSQLDA status: patches always welcome! I'm swamped with paying work right now, so it's sort of come to a stand still. All I've been able to do is grep the zope lists for mention of 'postgres' or 'pygres' and make sure no one's reporting big problems. So, if you have problems, be sure to report them! For more about PostgreSQL, see my post to the zope-dev list. Ross -- Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu> NSBRI Research Scientist/Programmer Computer and Information Technology Institute Rice University, 6100 S. Main St., Houston, TX 77005
participants (5)
-
Hannu Krosing -
Karl Fast -
Nitin Borwankar -
Phillip J. Eby -
Ross J. Reedstrom