> If we are talking about making a SQL application that is usable for > a multitude of people then why lock them into something. That's the > easiest way to drive them away from supporting it.
Word. Perl can play nice with plenty of RDBMSs. If this discussion belongs here at all, I can't see how RDBMS partisanship is going to take it anywhere good. FTR, there are several (commercial) spam quarantine applications, and at least three very big compliance/archival services, that take a SQL-based back-end as a given. Their traffic and access patterns have clearly been taken into account here, but nonetheless these are proof that the concept already has real-world purchase, depending on budget and application. --Sandy
