----- Original Message ----- From: "Jochem van Dieten" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Wednesday, July 30, 2003 3:00 PM Subject: Re: Access to MySQL Migration
> 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 Are you certain about the NOT NULL constraints? I'm aware of all the others. We'll probably move to 4.0.14 with InnoDB tables soon, so will have transactions and foreign key constraints at that point. The applications we're migrating right now aren't affected by either. The subqueries we're learning to rewrite. One thing we just noticed... MySQL recognizes C-style character escape sequences, beginning with backslashes. http://www.mysql.com/doc/en/String_syntax.html For instance SET foo = 'some \t text' inserts a tab in the middle of the string. This is biting us in migrating data fields containing backslashes. If not escaped (\\) the ODBC driver throws an error. Anyone figured out an easy workaround? A lot of applications will also have to see extensive modification to deal with this little gotcha if we can't disable the behavior. Jim ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. http://www.cfhosting.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
