> Both Gadfly and SQLite have DB-API compliant drivers and use SQL My apologies, I obviously gott confusd somewhere I thought Gadfly was a non SQL DB. In which case you can ignore my previous comments about Gadfly being less suitable than SQLite.
> .... I guess I see three rough categories. I'd agree with Kents summary. > At the top of the heap are the industrial strength databases. > This includes free products like MySQL, PostgreSQL and Firebird > as well as commercial products like MS SQL Server, Sybase and Oracle. The commercial ones all tend to scale better at the very big end of things. But you only need to worry if you have more than a thousand users or over a terabyte of data. For 90% plus of applications the freeware ones will do fine. > In the middle tier are databases that are not as full featured > but still very usable for small to midsize work. I would put > SQLite and Gadfly into this category. Some people would argue that MySQL > belongs here. I'd have put MySql here up until release 5 but its now pretty solidly in tier 1 territory - especially since their tie up with SAP and MaxDB for large data sets and with the addition of stored procedures. The other popular one in this tier 2 category is MS Access. > In the bottom tier are programs that are more of a persistence mechanism > than a true database. I put KirbyBase here along with the standard > Python shelve and dbm modules. The other category are the Object Databases like ZODB from Zope. However they are so disparate in capability and architecure that there is little in common. The big win with a SQL solution is that the knowledge transfers easily from one DB to aother as the size grows. Alan G. _______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
