8 thoughts

  1. Also note that you can get additional meta info for a query by calling getMetaData on the query object. See my blog post from last week.

  2. Seems both of these also work for stored procedures, although the result only returns execution time.
    I can see the getMetaData function being useful for writing generic data display screens, etc.

  3. hi, Ben, we know cf6 supports mysql from 3.x to 4.x very well in double bytes, but cf7 only supports mysql 3.x , and we can let it support mysql 4.x by using the newest connecter-J ,but when I use
    "useUnicode=true&characterEncoding=gb2312" to connect with mysql, that does not work,I have tried to connect it with "useUnicode=true&characterEncoding=UTF8", and that also just outputs arsy-varsy code. Could help me?

  4. While we’re on the subject, the interested parties
    should note that there’s an error in the help
    page that Macromedia has released for cfquery’s
    "result" attribute. It says
    name = "query_name"
    dataSource = "ds_name"
    dbtype = "query"
    username = "username"
    password = "password"
    maxRows = "number"
    blockFactor = "blocksize"
    timeout = "seconds"
    cachedAfter = "date"
    cachedWithin = "timespan"
    Either of the following:
    debug = "yes" or "no" or: debug
    result = "result_name"
    The CFMX7 help-extensions for Homesite and Dreamweaver MX contain this error.

  5. You can also access the query collection, sort of like you might with an ADO recordset, inside another query ad hoc like this: #queryname.columnname[i]#. Pretty handy in CF 5 hosting sich’es where you can’t query a query, have subqueries, etc.

Leave a Reply