Benefits of Using CFUPDATE/CFINSERT (was RE: NOT A CRITICAL ISSUE - CFUPDATE vs CFQUERY UPDATE tablena me e tc.)

2003-03-18 Thread Scott Wilhelm
What would I gain by using CFUPDATE/CFINSERT over CFQUERY? THanks, Scott -Original Message- From: Edwards Robert (air0rae) [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2003 2:24 PM To: CF-Talk Subject: RE: NOT A CRITICAL ISSUE - CFUPDATE vs CFQUERY UPDATE tablena me e tc.

RE: Benefits of Using CFUPDATE/CFINSERT (was RE: NOT A CRITICAL ISSUE - CFUPDATE vs CFQUERY UPDATE tablena me e tc.)

2003-03-18 Thread Douglas.Knudsen
well, you would not gain the esteem of your peers here for sure!! LOL! Best to roll your own SQL. Doug -Original Message- From: Scott Wilhelm [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2003 3:26 PM To: CF-Talk Subject: Benefits of Using CFUPDATE/CFINSERT (was RE: NOT A

Re: Benefits of Using CFUPDATE/CFINSERT (was RE: NOT A CRITICAL ISSUE - CFUPDATE vs CFQUERY UPDATE tablena me e tc.)

2003-03-18 Thread Bryan Stevenson
Nothing.just easier to code with CFUPDATE/CFINSERT. CFQUERY using CFQUERYPARAM will help to stop SQL injection attacks, use BIND variables to increase performance (not all DBs use BIND vars), and won't bail on you all the time like CFUPDATE/CFINSERT. Bryan Stevenson B.Comm. VP Director of

RE: Benefits of Using CFUPDATE/CFINSERT (was RE: NOT A CRITICAL ISSUE - CFUPDATE vs CFQUERY UPDATE tablena me e tc.)

2003-03-18 Thread Mosh Teitelbaum
CFUPDATE and CFINSERT tend to let you get away with not knowing SQL. But using CFQUERY and SQL give you much greater control over your queries. It's really a matter of preference. Personally, I won't use them. I'd rather have near complete control over my database interactions. -- Mosh