Today I wrote a function that added in default rows to a query. Part of the function needed the text of a query to find the default values. I attempted to pass in the query text and use the same text in a <cfquery> tag. This did not work. Here is the query I passed in: SELECT This, That FROM Those WHERE bar = 'foo' ORDER BY SortOrder Here is the resulting error: Error: [Macromedia][SQLServer JDBC Driver][SQLServer]Incorrect syntax near 'Foo'.

I've been reading Sean Corfield's examples on how to use the Closure library. This still seems a little mystical to me since I haven't made use of closures in programming before.To ease my befuddlement, I wrote a test for the Closures library. The use case for the below example is summing a column that contains non-numeric values.

The "frighteningly" evangelistic Rey Bango, newly anointed into the JQuery Evangelism fold is a long time ColdFusion programmer. Rey kicked off a new project called gotCFM.com to spread the good word about the vitality and strengths of ColdFusion and CFMX. There is an article on Digg.com at the moment and it could use an few nudges north. Give a Digg for ColdFusion, would ya? Still need convincing?

Sean Corfield pointed out that using ColdSpring to make instance (throwaway) components is quite a heavyweight approach for a simple form bean. He is, of course, correct. Our ContactFormBean is currently created by ColdSpring. In this series, we will add a factory object that will make our instance beans for us. The factory itself will be configured through ColdSpring as well as the configuration for our objects. This is a very simple factory.

In our last segment we built the functionality to store our contacts to the database. Now we need a way to edit the information because after all, friends can become enemies, and enemies can become co-workers. We have a good structure in place and these changes will be simple.

In our last series, we moved the ContactTypes from a ColdSpring configured struct, to a database table. This set the stage to move the rest of our persisted data to the database. As we begin this series our main goal is to have our contacts and lists of contacts stored in our database. Originally, we used in-memory storage as it allowed us a functional application without a database. In this series, we will introduce two new files, ContactDAO and ContactGW (GW = Gateway).

We are going to break this up into phases starting with the contact types. At the end of this series, our contact types will come from the database and we will have an even greater appreciation for ModelGlue and ColdSpring. The last article gave the spec for your database tables, Contact and ContactType. Add in 3 dummy records to the ContactType table. I used Friend, Enemy and Co-worker. Set up your datasource in the ColdFusion administrator. I used the data source name of 'ContactOMatic'.

In the next few series, our Contact-O-Matic will persist data in a database. The queries and relationships are simple and should translate over to any database. Our code will be organized into two types of components the DAO (Data Access Object) and the Gateway. These two components are common structures used in many Object Oriented systems and a quick google search will land you on endless descriptions for each.

I am planning out the next few steps in our ModelGlue:Unity series and would like to tally a vote. Currently our Contact-O-Matic is barebones. We went over how to use portions of ColdSpring to manage our service and to pass in configuration parameters. We also went over adding ModelGlue results to change the programmatic flow of the application. Following this pattern, you should have a good base on ModelGlue:Unity. However, apart from the tabs, it has a plain-jane look and feel.

Previously in this series, we installed the ModelGlue:Unity framework and the ColdSpring framework. We used the ModelGlueApplicationTemplate as the skeleton, added our basic flow and navigation. We can save and list contacts and our validation is working nicely, In this section of our Contact-O-Matic, we will pull out the contact types values from coldspring and used them to add defined categories to our contacts.