Thanks for the information. Now that you mention it I had observed an unquoted string going into one query when the DataType was UNKNOWN. In that case it was a bug of an improperly defined column. I didn't think of it as a feature. Perfect.
On Sat, Jan 23, 2010 at 10:58 AM, Rainer Döbele <[email protected]> wrote: > Another way should be to override useCmdParam() in DBCommand, which tells the > Command class whether to add the value to the SQL string directly or add it > as a command parameter. Unfortunately this function is private instead of > protected with is a mistake. Do you think DBOrderByInfo could be made public too? I was trying to leverage it to not duplicate its (albeit simple) addSql method for use in the ROW_NUMBER example. It was protected so it was off limits for that purpose. Thanks for considering the patch. It seems to work fine in MySQL and SQL Server for me so far. Thanks, McKinley
