Jon,

The other way around.  Using real sql for updates and inserts is far faster 
and better than cfinsert/cfupdate.  Real sql should be used on a NT 
environment as well.  Its best not to have cf  try to interpret things and 
do the extra work, especially when you have large amounts of 
traffic.  (cfinsert/update is definitely easier to code but not by much)

I'll have to test that new app.  I thought the myodbc was the only 
one.  Thanks for the link!

Brett

At 12:53 AM 12/29/00 -0800, you wrote:
>Brett, are you saying that in high traffic circumstances, it is beneficial 
>to use cfupdate and cfinsert?  Or is it simply easier to code?
>
>Also, the mysql database utility that we have been using for greater than 
>a year is MySQL Admin for windows.  it is a sweet 200K app that does 
>everything you need to do with mysqld.  I
>dont know where it is now...i found it at www.mysql.com...but you can 
>download it here:
>
>http://www.enthusiastonline.com/mysqladmin.zip
>
>I have used the ACCESS2MYSQL script quite a bit on very large databases 
>and it works great.  Large text fields such as "MEMO" in access come out 
>as BLOB in mysql and can then be changed
>to TEXT.  Also, the autoincrement from access sometimes has 
>problems.  When performing this on large databases, a very large text file 
>will be generated with all the data from Access.
>In my experience, I had to use Word to cut down the files into 500 record 
>increments because my server would hang because of buffer limitations, but 
>try it for yourself.
>
>I have been very pleased with mysql and I love giving out info to further 
>convince others of this free robust solution.
>
>Jon Cline
>Enthusiast, Inc.
>www.enthusiastonline.com
>[EMAIL PROTECTED]
>
>Brett Frisch wrote:
>
> > Gilson,
> >
> > 1. Dustin is correct with the cfupdate and cfinsert not working in
> > Linux.  Its a known bug that was supposed be fixed in sp2 (I believe
> > anyway).  Use the standard sql insert and update.  When your site gets lots
> > of traffic, using those two will keep your db happy!
> >
> > 2.  Mysql doesn't support transactions.  Probably won't for awhile or maybe
> > never.
> >
> > Also, I don't know if your have MS Access on hand or not but,
> > http://www.mysql.com has a odbc tool that converts access to mysql.  You'll
> > have to import your sql data into ms access then odbc to new mysql
> > db.  I've only used it once and it worked well (on a small set of
> > tables.  If your db is robust I might question its ability).  I make the
> > db's by hand in mysql now (it seems faster for me) so I can't tell you
> > anything anything more than that.  Here's the direct
> > link:  http://mysql.com/downloads/api-myodbc.html
> >
> > Brett
> >
> > At 12:01 AM 12/29/00 -0700, you wrote:
> > >Gilson,
> > >
> > >I just completed a conversion from NT/MSSQL to Linux/MySql.  Couple of
> > >things to note:
> > >
> > >1. As Steve said, filenames are now case sensitive.
> > >2. CustomTags are searched-for in the same manner as under Windows -- 
> under
> > >Linux, it MUST be in the CUSTOMTAGS directory.
> > >3. The MySQL ODBC Driver (by Merant) that ships with CF does NOT SUPPORT
> > >TRANSACTIONS. Therefore, using CFTRANSACTION will cause an exception.
> > >4. In MySQL, table names are case sensitive, but everything else is not.
> > >5. I used @@IDENTIY values in MSSQL, so had to convert those to AUTO
> > >INCREMENT values in MySQL.
> > >6. CFINSERT and CFUPDATE do not appear to work with MySQL.
> > >
> > >I think those are about the biggest GOTCHAS I have found so far.  Now, I'm
> > >off to stress testing!
> > >
> > >-Dustin
> > >
> > > >
> > > > Date: Fri, 29 Dec 2000 00:22:29 -0200
> > > > From: Gilson Soares <[EMAIL PROTECTED]>
> > > > To: [EMAIL PROTECTED]
> > > > Subject: Re: Porting from Win2K to Linux
> > > > Message-ID: 
> <[EMAIL PROTECTED]>
> > > >
> > > > Thanks Steve.
> > > > I will start the port next week. I will try to record all issues 
> and tell
> > > > you the results.
> > > >
> > > > Happy New Millenium.
> > > >
> > > > At 28/12/2000 11:47 -0500, you wrote:
> > > > >Be careful of your case sensitivity with filenames dealing with
> > > > >cfinclude/cfmodule, custom tags, Application.cfm and OnRequestEnd.cfm.
> > > > >Also at the web server level with image case sensitivity.  If you're
> > > > >using Apache, you can try the mod_speling to solve the problem 
> with the
> > > > >images.  The .cfm's you have to do check by hand.
> > > > >
> > > > >I'm not sure about the DB2 port, but I imagine that should move over
> > > > >just fine.
> > > > >
> > > > >Steve Nelson
> > > > >http://www.SecretAgents.com
> > > > >Tools for Fusebox Developers
> > > > >(804) 825-6093
> > > > >
> > > > >
> > > > >Gilson Soares wrote:
> > > > > >
> > > > > > Hi everybody,
> > > > > >
> > > > > > I have a ColdFusion application (around 260 CFM in Fusebox)
> > > > running ok with
> > > > > > DB2 on win2k (I personally prefer Linux).
> > > > > > It's time to deploy it. I just received a server box to try 
> running it
> > > > > > under Linux, ie CF-Linux and DB2-Linux.
> > > > > >
> > > > > > Has anyone made this migration before (even not using DB2) ?
> > > > > > Has any cautions that I am be aware off?
> > > > > >
> > > > > > PS: All Custom Tags I use are strictly CFM. No objects, OCX, 
> C++, etc.
> > > > > >
> > > > > > Thanks
> > > > > > Gilson Soares
> > > > > >
> > > > > >
> > > > >
> > > >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-linux%40houseoffusion.com/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_linux or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to