Admittedly, I'm away from my OpenBD installation at the moment, but I think that already works:
<cfset queryAddColumn(qryThis,"column",arrayNew(1))> - fails due to required 3rd arg. (in openBD) <cfset queryAddColumn(qryThis,"column","varchar",arrayNew(1))> - works (from memory) I think you're being a little harsh about storing rich objects in a query. After all, queries already support binary objects. Whether or not it's dumb, it is a compatibility issue, which is what I thought we were shooting for here. On Jan 5, 12:05 pm, "Alan Williamson (aw2.0 cloud experts)" <[email protected]> wrote: > Yes, we may as well square that hole > > Alex Skinner wrote: > > Yes the fact that you can store rich objects in a query you create is > > dumb in the extreme as it breaks so many other parts that don't know > > what to do when they encounter them. > > > One thing that I believe is not supported in OpenBD which i think is > > in ACF is the idea of adding a blank column so in the value array > > field passing a blank array > > > QueryAddcolumn ( query, column, datatype, /arrayNew(1)/) > > > Now this can easily be got around in a sql query by just doing > > something like '' as nameofcolumn but worth mentioning > > > Shall I raise a bug ? > > -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012
