Ben Nadel © 2008.
All content is the property of Ben Nadel and Kinky Solutions.
The ColdFusion query object is such a cool part of ColdFusion. And, I'm not just talking about getting data from a database. I'm talking about building queries from scratch and maintaining them programmaticly. The only small rub I can see in the situation is the fact that the data types used when creating a query are different from the ones used to set query cell values.
When you create a query via QueryNew(), you have the option to pass in a list of column names and column types. Or, you can leave these blank and add individual columns to the query, again passing in a column name and data type (and an array of values). When doing either of these, the possible data type values are:
So, for example, if I wanted to create a simple query using data types, I could do so like:
Launch code in new window » Download code as text file »
Here we are explicitly telling the query to be instantiated with three columns. We are also telling it that the underlying data types of the columns are Varchar, Integer, and Bit. Now, here's the weird thing: ColdFusion is typeless, but query object data is not really typeless. Anyone who has manually altered a query and tried to run a query of queries probably has come across type conversion errors. That's because under the surface, these data types have to map to Java data types when running non-typeless SQL statements.
Now, how do you make sure that you set query cell data values with the proper type? You have to use JavaCast():
Launch code in new window » Download code as text file »
As you can see in this example, the Java data types are not exactly the ones that I chose for use in the QueryNew() call. That's because the set of Java data types is different:
It's gets a bit sticky when you see that there is not a Java data type for every QueryNew() data type. Take Date and Time for instance. There is no date or time data Java data types listed. If you need to set a value into a DATE field, you can pass in any value that can be interpreted as a date. In ColdFusion (and other languages), dates have both a string representation and a numeric representation. Take the date 01-01-1980 for instance. That can be represented in a query by any of the following:
The first is the string time-stamp. The second is a float. The third is either an integer, long, or double. Therefore, when you need to set a date field manually, you can use any of the Java types string, int, long, float, or double.
But, that's for DATES only. If you need to set a date AND time value, it gets a bit tricky. Remember as a numeric value, the time is the decimal part of the floating point number. In that case you NEED the floating point number. No passing in int, long, or double as your data type. Only string or float will do.
I am not even sure how you would map the byte array QueryNew() data type from the Java types. But, I have not come across that yet, so no worries.
But any ways, be careful when you are setting query values. You cannot just throw typeless values into these cells. Remember, ColdFusion is typeless but SQL is not. Therefore, when you run a query of queries using SQL (a subset of), you CANNOT assume that ColdFusion will type everything out correctly. You have to be explicit.
Download Code Snippet ZIP File
Comments (0) | Post Comment | Ask Ben | Permalink | Other Searches | Print Page
Skin Spider : The "No Framework" Framework
Restarting Windows Explorer Without Restarting Your Computer
There are no comments posted for this web log entry.