[cfaussie] RE: Opinions on naming form fields the same as db columns...

Wed, 11 Feb 2004 20:13:57 -0800

Title: Message
yes it is supposed to be..
 
 
Taco Fleur

Tell me and I will forget
Show me and I will remember
Teach me and I will learn
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Walker
Sent: Thursday, 12 February 2004 1:31 PM
To: CFAussie Mailing List
Subject: [cfaussie] RE: Opinions on naming form fields the same as db columns...

I think qContact is supposed to be qMyQuery

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Evans
Sent: Thursday, 12 February 2004 3:26 p.m.
To: CFAussie Mailing List
Subject: [cfaussie] RE: Opinions on naming form fields the same as db columns...

 

Can someone fill me in on what the qcontact construct is?

 

Thanks,

Phil.

 

----- Original Message -----

Sent: Thursday, February 12, 2004 2:12 PM

Subject: [cfaussie] RE: Opinions on naming form fields the same as db columns...

 

I agree – you can’t rely on people not guessing your column names. I call them the same where possible.

 

You can btw write:

 

<cfset form[variables.column] = qContact[variables.column]>

 

 

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Taco Fleur
Sent: Thursday, 12 February 2004 2:53 p.m.
To: CFAussie Mailing List
Subject: [cfaussie] Opinions on naming form fields the same as db columns...

 

I am have been using the same naming convention and names for my DB columns as for my form fields (or vice versa), this allows for simple form population like following

 

<cfquery name="qMyQuery" datasource..........>

SELECT        blah, blah

FROM.................

</cfquery>

 

<cfloop index="column" list="#qMyQuery.columnList#">
  <cfset setVariable("form.#variables.column#", qContact[variables.column])>
</cfloop>

 

I can already hear people saying "but then all crackers know your column names" etc. etc.

I am aware of this, personally I think this is something not to really worry about, as they can easily be guessed unless you are using some very cryptic names for your columns. Second, if they have come to a point where they could actually do something with those column names it would be just as easy to get them at that stage.

 

Another advantage is that you never have to mix and match form fields with column names....

 

Anyway, what I am looking for is negativity from you guys ;-)) Tell me why I should really not do this...

 

Taco Fleur

Blog http://www.tacofleur.com/index/blog/
Methodology http://www.tacofleur.com/index/methodology/


Tell me and I will forget
Show me and I will remember
Teach me and I will learn

 

---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

Reply via email to