History for RDBMSAndZope
??changed:
-
There are quite a few Database options for use w/ ZOPE. The main problem is the only ones that 'really solid' are the most commonly used ones (hopefully this isnt a problem! unless you are using something really ecentric). Check out the "Products":/Products for a database adapter for your needs.
* Commercial Based
* Oracle - this is probably the most mature database adapter, since most, if not all of DC's clients probably use it! The Oracle native client is usually supported on top of Unix. The NT one could probably be made to work but would need to some hacking or some support for DC.
* Sybase - another commonly used one. This was told to me by cpetrilli.
* Community Based
* SAP DB 7.3 - a great vendor supported database. SAP has release this database as an Open Source in 3rd quarter 2000. It has replication, online backup, stored procedures. This is a big player equivalent to the four majors(ORACLE,DB2, MS SQL Server, Sybase ASE )
* MySQL - a great lightweight fast free database. the drivers seem to me to be really solid (I use it, quite a bit - but low levels of activity). I believe it supports threading.
* PostgreSQL - Works well with Zope, and has many advanced features similar to larger, commercial databases. There are three adapters for Zope: ZPygreSQL (the oldest; easy to install, but lacks threading features for high-volume use); ZPoPy (more modern, but little recent development), and psycopg (modern and actively developed).
* Interbase - there is a Interbase FileStorage, so I would imagine there is a ZOPE database adapter. if not it wouldnt be too much of a stretch to make one or have one made.
* ODBC - you can use ODBC on Microsoft platforms. Works well w/Microsoft Access. It appears that ZopeCorp has abandoned this project, though -- there hasn't been any real work on it since late 1999.
* DBI - this is brand new. Active State and Digital Creations in effort to get PERL as a scripting language on the ZOPE platform has, as a by product, exposes importing of Perl's mature DBI module. You have access to *LOTS* of databases through this with one caveat. Perl does not support threading. so for intensive and multithreaded access to the DBI module is probably not a forseeable in the next few months.
*NOTE* how you interact w/ the database is using SQLMethods. this is very interesting way of looking at database interaction and 'seperation of logic' managing all 'layers' under one umbrella. (pauls mantra - should probably be more explicit WHY, this is a good thing :)