So you want to create a CFWheels application? (Part 6)

This CFWheels series is heavily borrowed from Dan Wilson's "So You Want to" series about Model Glue:Unity and matches to this post. Previously in this series, we installed CFWheels, discussed some concepts in CFWheels, added our basic flow and navigation, created add and list functionality, added validation, and talked in more detail about the CFWheels ORM. Here is a zip, if you want to start from this post. Unzip it in an empty webroot. Today, we will cover the CFWheels ORM a little more. Specifically the return differences between some built in ORM calls and the logic why, specify the SQL order by clause and other sql fine-tuning, and build update and delete functionality. Let's create an edit action in /Models/contact.cfc:

Now add this to the end of the first tr tag. And add this code to to the end of our last tr tag. in \\views\\list.cfm. \\views\\list.cfm should look like this now. Click on an Edit link and you should see this: What you see here is two objects and one query. You may think this is odd since you are using the CFWheels built in ORM and you thought the ORM calls would return the same structure. I thought the same thing but when talking to Per Djurner, it made perfect sense. Here is (http://groups.google.com/group/cfwheels/browse_thread/thread/bbe87f459b7a294c/8f4a1c09a37d1814?lnk=gst&q=object+query#8f4a1c09a37d1814): "The convention is that when you are fetching a single record from the database (using findOne, findByKey etc) you will get an object back.When you are fetching multiple records you will get a query result set back. The "returnAs" argument is a way to override this convention (and it will be improved a little more before we release 1.0)." "The reasoning behind the convention is that when you are asking the database for multiple records it is likely that you intend to display them (rather than edit/delete them). In this case objects are overkill (and even more so because of the poor performance of object creation in ColdFusion)." See the CFWheels guys are always thinking. Don't be afraid to ask @ the (http://groups.google.com/group/cfwheels). One other thing, I would like to point out is . See how, I easily added a where clause. This get the same results as . , and accept arguments as you can see from above. We are using the where clause and include for Associations. They also accept select, order, maxRows, and a couple arguments for pagination and caching. For more (http://cfwheels.org/docs/chapter/reading-records). Remove from our edit action: Test our Edit link again, and then update the contact. It should update the contact and return us to the List page For more (http://cfwheels.org/docs/chapter/updating-records). Lets add order by to our list action in controllers/contact.cfc. Replace with And reload our list again. See the SQL now has an "Order By" clause. Lets wrap this entry up by adding delete functionality. Go to /Views/list.cfm, and add after . In /Controllers/contact.cfc add: Load our list again and you should see the delete link. Give it a try. Success! For more (http://cfwheels.org/docs/chapter/deleting-records) We have a fully working Contact-O-Matic Application. Next in the series, I'll talk about Routing and Plugins in CFWheels.