We run CF5 and never have had problems with CFform...I don't
particularly like using it b/c its just as easy to write validation on
your own but I've done some pretty nice things with it. CFform isn't
all bad. :)
Adam H
On 5/12/05, Glenn Saunders [EMAIL PROTECTED] wrote:
At 08:20 PM 5/11/2005,
I guess we all have our admamant areas :) If I see a Select * I get
fairly upset with the developer. In most caees you are bringing back
unneeded data and in a large developement envirmoent another programer
can not easily step into the code and see what is being selected from
where.
Adam H
On
OK, I'll bite. Why would you *not* use standard CFML tags for the
purpose they fullfill?
--
Damien McKenna - Web Developer - [EMAIL PROTECTED]
The Limu Company - http://www.thelimucompany.com/ - 407-804-1014
#include stdjoke.h
-Original Message-
From: Glenn Saunders [mailto:[EMAIL
CFINSERT and CFUPDATE are nice shortcuts, but they're wierd. You're
required to have your variable names match the exact column names in the
DB, which, unless you have planned for that from the beginning, almost
always requires you to write unnecessary cfset applicationVar =
translatedDBVar
Glenn Saunders wrote:
But for most CF applications, that degree of optimization is overkill in
comparison to the extra keystrokes it takes to do variables. I find this
code:
CFSET variables.a = 1
CFSET variables.b = 1
CFSET variables.c = 1
CFSET variables.d = 1
CFSET variables.e = 1
Glenn Saunders wrote:
To me, the convenience of all those built-in validation functions is too
compelling for me to write my own JS validators, and I prefer to have as
much JS validation as I can rather than just relying on server-side
validation.
My problem with trusting the built-in
Why this is in the cf-jobs-talk forum, I don't know. But, since it's
here... forget cfform and check out QForms by www.pengoworks.com The only
form validation tool you will ever need. Look under javascript on their
website for the QForms API.
Rob
From: Scott Brady [EMAIL PROTECTED]
At 07:35 AM 5/12/2005, you wrote:
OK, I'll bite. Why would you *not* use standard CFML tags for the
purpose they fullfill?
Well, for one thing, because CFINSERT and CFUPDATE don't call stored procs
and we do almost all our db work via stored procs.
With CFQUERY you can do CFQUERYPARAM to help
CFQUERY will not return back a new identity either, well depending on the
database chosen it will not without a second cfquery. Just curious, not
implying anything wrong with it one bit, but what are your reasonings for
using almost all SPs for your DB work? Also curious the reasons for that
At 09:12 AM 5/12/2005, you wrote:
At 09:00 AM 5/12/2005, you wrote:
CFQUERY will not return back a new identity either, well depending on the
database chosen it will not without a second cfquery.
This has sometimes worked in the past:
declare @new_id INT
insert into table (a, b)
values
That syntax is not even valid for all databases. An example I am thinking of
is how to return the identity when using Oracle. I know the syntax to use if
just in a SQL client, tried it with a couple of versions of DB drivers with
CF and never had it work. Of course it could simple just be done
At 09:18 AM 5/12/2005, you wrote:
CFLOCKing two queries together? Wouldn't that be CFTRANSACTIONing the two
queries together?
Well, the examples given with the select max(id) are so ugly, don't even
consider doing it, but since it's in at least one of the CF books a lot of
developers got set
with oracle vernacular the word is sequence. Just perform a query to return
the next value in the sequence, then use it in your inserts.
SELECT seqname.next_val as newid FROM dual
INSERT INTO tablefoo (id, goo) VALUES (newid, 'soem stuff')
DK
On 5/12/05, Aaron Rouse [EMAIL PROTECTED] wrote:
Or the simplified version of the example
INSERT INTO tablefoo (id, goo) VALUES (seqname.next_val, 'soem stuff')
--
Ian Skinner
Web Programmer
BloodSource
www.BloodSource.org
Sacramento, CA
C code. C code run. Run code run. Please!
- Cynthia Dunning
-Original Message-
It is SEQNAME.NEXTVAL in Oracle and I'd like to see how you get that to work
in a single CFQUERY that returns NEWID to the CFM page. Using two CFQUERies
would at least avoid the need to lock anything.
On 5/12/05, Douglas Knudsen [EMAIL PROTECTED] wrote:
with oracle vernacular the word is
Which still does not return the unique identifier(the value of
SEQNAME.NEXTVAL) to the CFM page. The lack of returning a the unique
identifier was one of the big hang ups given against CFINSERT. A simple
trigger in the database and making sure form fields use the same names as
columns would
there is no need at all to lock anything. Once you get the nextval from the
sequence, it is yours to keep. Another thread, request, user what have you
will get a differnt value guarnteed.
You will have to use two queries to return the value though, but again, no
locking is needed.
DK
On
Funny I was going to use DAO as an arguement for using Select * but
didn't bother since I didn;t want to mix entry level using select *
with using Select * with a DAO Design Pattern which if you are using
DAO you're not entry level. I could just as Easily say though (just
for arguements sake) that
Except that's 2 places... 1 in the database and 1 in the code... 2...
:)
I wouldn't call that lazy -- you'd be _amazed_ how much time you can
save (and productivity you can gain) by cutting out very small
(microscopic) tasks which occur often. At least for me, I consider
schema changes at least
19 matches
Mail list logo
