Yes.
That's all well and good.

However...two tags which are very commonly used in application design,
were working before the update...and are not working now.

You can't expect us to change code..both which we have written in the
past, or which clients that we host have written to NOT use CFINSERT and
CFUPDATE because of applying Redsky.

So...there is a problem.
And I'm wondering if anyone has found a fix to it, because it doesn't
seem that we're the only ones experiencing this.

-Gel

-----Original Message-----
From: Matt Robertson [mailto:[EMAIL PROTECTED] 

Hi Angel,

Didn't we discuss this in another forum (i.e. the overall value of these
tags in CFMX; the question being have they grown up and are ready for
widespread use)?  I recall saying in one of those posts that these tags
blackbox your sql and return unhelpful error messages, making them too
much trouble to mess with (among other cited weaknesses).

My opinion, which I know some disagree with, remains that this is a tool
only suited for beginners who don't know sql yet.  More often than not
if you try to use it past that level you'll find that what you thought
was a time-saving feature just isn't, given the extra time you have to
take dealing with stuff like your current problem cropping up out of
nowhere, or gymnastics necessary to input a limited field set, copy vars
to the form scope etc. etc.  

If you write real sql you will be done with it forever, unless you
change your own app.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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
                                

Reply via email to