RE: Access to MySQL Migration

2003-08-01 Thread Matt Robertson
to MySQL Migration Matt Robertson wrote: Jochem wrote: NOT NULL constraints You mean a simple NOT NULL in a field spec? mySQL supports that, and should have back to 3.23 when I started using it. I'd hope if something like that was missing I'd have noticed :D quote If you insert

Re: Access to MySQL Migration

2003-08-01 Thread Jochem van Dieten
Matt Robertson wrote: I've always thought of mySQL as an upscale Access that's the next logical step when your traffic overburdens the weak Access engine but your budget or needs aren't in league with a true grownup solution. This sort of malarkey reinforces that. I think MySQL is very

Re: Access to MySQL Migration

2003-08-01 Thread John Paul Ashenfelter
Subject: Re: Access to MySQL Migration Matt Robertson wrote: I've always thought of mySQL as an upscale Access that's the next logical step when your traffic overburdens the weak Access engine but your budget or needs aren't in league with a true grownup solution. This sort of malarkey

Re: Access to MySQL Migration

2003-07-31 Thread Jochem van Dieten
Jim McAtee wrote: How exactly does cfqueryparam fix this? I just modified a tiny application I wrote which now uses a MySQL table to track query history. Using cfqueryparam did indeed fix the problem, but I can't really tell what it's doing. My cfquery, which looks like cfquery

RE: Access to MySQL Migration

2003-07-31 Thread Matt Robertson
Jochem wrote: NOT NULL constraints You mean a simple NOT NULL in a field spec? mySQL supports that, and should have back to 3.23 when I started using it. I'd hope if something like that was missing I'd have noticed :D decimal datatype Its there, too. I found CREATE TABLE scripts dated back to

Re: Access to MySQL Migration

2003-07-31 Thread Jochem van Dieten
Matt Robertson wrote: Jochem wrote: NOT NULL constraints You mean a simple NOT NULL in a field spec? mySQL supports that, and should have back to 3.23 when I started using it. I'd hope if something like that was missing I'd have noticed :D quote If you insert a 'wrong' value in a column

Access to MySQL Migration

2003-07-30 Thread Jim McAtee
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? Thanks, Jim

Re: Access to MySQL Migration

2003-07-30 Thread Jochem van Dieten
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

Re: Access to MySQL Migration

2003-07-30 Thread Jim Campbell
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

Re: Access to MySQL Migration

2003-07-30 Thread Jim McAtee
- 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

Re: Access to MySQL Migration

2003-07-30 Thread Jochem van Dieten
Jim Campbell wrote: Transactions and foreign keys are available in MySQL by using the InnoDB engine. But the OP said MyISAM. 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).

RE: Access to MySQL Migration

2003-07-30 Thread Barney Boisvert
] voice : 360.756.8080 x12 fax : 360.647.5351 www.audiencecentral.com -Original Message- From: Jim Campbell [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 2:54 PM To: CF-Talk Subject: Re: Access to MySQL Migration Transactions and foreign keys are available in MySQL

Re: Access to MySQL Migration

2003-07-30 Thread Jochem van Dieten
Jim McAtee wrote: From: Jochem van Dieten [EMAIL PROTECTED] Jim McAtee wrote: 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

Re: Access to MySQL Migration

2003-07-30 Thread Jim McAtee
- Original Message - From: Jochem van Dieten [EMAIL PROTECTED] To: CF-Talk [EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 4:44 PM Subject: Re: Access to MySQL Migration One thing we just noticed... MySQL recognizes C-style character escape sequences, beginning with backslashes

RE: Access to MySQL Migration

2003-07-30 Thread Jim Campbell
, MySQL is *really* good at rounding! Thanks - you learn something new every day. - Jim -Original Message- From: Jochem van Dieten [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2003 5:32 PM To: CF-Talk Subject: Re: Access to MySQL Migration Jim Campbell wrote: Transactions