Yeah, perhaps true but truthfully mySQL smokes as a readonly filesystem... Different tools for different problems.
Hey while you're at it maybe one of you geniuses can help me get my head around my problem with CFMX vs CFM5 causing a "Refresh to Repost the Form Data" notice on the exact same code but with only the server being different. I have a two urls available I can send off list to test with if you think you might have an idea. The current discussions today (RE: CFMX caching...) give insight but still no Cigar! Any takers? At 11:28 PM 7/9/02, you wrote: >You may be shocked to realize that I disagree. While conforming to the >exact definition of an RDBMS doesn't require one to be ACID compliant, >it is assumed that ACID compliance is a standard feature of a database. >If you want to debate on definitions then surely I would lose. However, >if you take a look at the expectations of database customers, you will >see that ACID compliance is assumed. Thus, any RDBMS that isn't ACID >compliant should be pointed out as such to keep people from finding out >the hardware. > >If you want to talk theory a little then you might look at what >functionality differentiates a database from a file system. You might be >surprised to learn that MySQL is closer to a SQL front-ended file system >than the traditional idea of a database. Again, ACID compliance being >the main difference. > >For those interested in history, you might check out MySQL's roots. >Again you will see that MySQL started out as a really complex file >system that is slowly making its way towards that of a traditional >database. > >Matt Liotta >President & CEO >Montara Software, Inc. >http://www.montarasoftware.com/ >V: 415-577-8070 >F: 415-341-8906 >P: [EMAIL PROTECTED] > >> -----Original Message----- >> From: Dave Watts [mailto:[EMAIL PROTECTED]] >> Sent: Tuesday, July 09, 2002 11:21 PM >> To: CF-Talk >> Subject: RE: Access on CFMX Linux? >> >> > Generally speaking, nothing should be referred to as a >> > database unless it is ACID compliant. >> >> That seems like an awfully stringent definition. How do you justify >that >> restriction on a common term of art which generally is interpreted >pretty >> broadly? There are lots of databases that aren't adequate for handling >> transactions, but that doesn't mean they're not databases. They might >not >> be >> GOOD databases, but that's another thing entirely. >> >> Dave Watts, CTO, Fig Leaf Software >> http://www.figleaf.com/ >> voice: (202) 797-5496 >> fax: (202) 797-5444 >> > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
