> One could argue (quite successfully IMHO) that's it's quite an
> *advantage* of MySQL to only add the overhead of supporting
> transactions to database tables that require that functionality and to
> be able to make that choice on a per-table basis. And to be able to
> change that decision ("hey, we *do* need transaction support on the
> orders table, bob!") with a simple ALTER TABLE statement.One could also argue that the ability to flip-flop like that can lead to data corruption (like NULLs in NOT NULL fields etc.). This is why I find Oracle difficult to deal with (try renaming a column in 8i...wholly crap)...it makes some more common changes very laborious just to ensure data integrity. So I prefer MS-SQL...keeps data integrity...but makes common data structure changes easier...but not too easy...it's a nice middle ground between MySQL and Oracle. We're all right in our own minds ;-) Cheers Bryan Stevenson B.Comm. VP & Director of E-Commerce Development Electric Edge Systems Group Inc. phone: 250.480.0642 fax: 250.480.1264 cell: 250.920.8830 e-mail: [EMAIL PROTECTED] web: www.electricedgesystems.com.cfm/54 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:208110 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
