WO and criteria for choosing a database server
WO and criteria for choosing a database server
- Subject: WO and criteria for choosing a database server
- From: David Holt <email@hidden>
- Date: Thu, 15 Dec 2005 14:52:58 -0800
Following on to the "images in the database" discussion from earlier in the week, I have been searching the archive for "Which Database?" discussions. So far my experience tells me that WO makes up for the limitations of databases such as MySQL for small applications under moderate load. I came over from the world of PHP and found data validation, referential integrity, and transaction support built right into the WO frameworks. Here are some of the external factors that I can think of that would influence a decision for choosing one database over another to use with WO:
1. performance under load is much better in some databases
2. price (of course)
3. there are data types that are not available in all databases
4. some databases have better administration/maintenance tools
5. encryption (communication and storage) is supported in some databases
6. you're dealing with legacy systems
Since WO abstracts away from the database so well, does it really matter which database you choose? Does it come down to personal preference? I have come across arguments for using almost every major database in the archives (most of them quite dated). My question is whether anyone has had any WO experience with a recent version of a database server that would tell you to never use it again for WO applications? If not, what criteria do you currently use to choose the database(s) you are using for WO? Here is the current list of officially supported databases from the Apple WO page:
Database servers
▪ Microsoft SQL Server 2000 8.00.194
▪ MySQL 4.1.10a
▪ OpenBase 8.0
▪ Oracle 10g Enterprise Edition
▪ Oracle 9i Enterprise Edition Sybase ASE 12.5 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden