> You mentioned about
> "
> <cfquery name="UpdStuff" ...>
> UPDATE mytable
> SET OrderEntry_Date = <cfqueryparam
> value="#Form.OrderEntryDate#"
> "
> But here, it's a SELECT statement, besides,
> Form.OrderEntryDate does not contain "_date".
<cfquery name="GetStuff" ...>
SELECT OrderEntry_Date AS OrderEntryDate ...
</cfquery>
> You said "So, again, this isn't a bug. If you design
> a database schema for use with a CF application",
> the fact is, in lot of cases, databases are not
> designed for a particular client language, database
> design is essentially based on business requirements
> including business rules, it shouldn't and care less
> what language will be used to interface with it.
> That's exactly what my argument was, one should not
> attempt to "bend" a given database.
That's true enough, but still not a big deal. You're free to use one field
name in your database, and use another field name in your HTML form. So, I
don't really see this as a serious problem - while I generally would
recommend that you use the same names for your HTML form fields as your
database columns, I'd make an exception in this case.
Considering that this behavior has existed since CF 1.5, I think, I suspect
it's unlikely to change any time soon.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
