Transactions and foreign keys are available in MySQL by using the InnoDB engine. Subqueries might be "doable" via a workaround, be it through more complex joins, CF QoQ's or a mixture of the two (Don't know about the performance hit, though). Is the "decimal" data type that different from MySQL's "double"? I also thought NOT NULL was supported. I guess I'll have to go home and try it now... :)
- Jim Jochem van Dieten wrote: >Jim McAtee wrote: > > > >>We're moving a number of backend databases from Access2000 to MySQL 3.23 >>(MyISAM) tables. As with Access, we're using ODBC (CF5) to talk to the MySQL >>server. Any advice or gotchas we should be aware of? Things that worked in >>Access that won't work in MySQL? >> >> > >transactions >subqueries >foreign keys >decimal datatype >NOT NULL constraints > >Jochem > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
