Hi All, Can anyone confirm or deny this?
1.In pre mx when cf stored the recordset in memory it stored the columns in correct order - meaning the order specified in the select statement. After mx (or is it 6.1?) the columns are stored in memory alpabetically. 2.In pre mx a null value in the recordset was stored as an empty string. After mx (again it may be 6.1) the null is stored as a null, even though it appears as an '[Empty String]' when you dump the query via <cfdump>. This doesn't cause a problem when outputting via cf tags but it does cause a problem when accessing the recordset via the java query interface. It seems that a fair bit of java cfx tags I have written that use the query interface fail on point 2 with a NullPointerException error and cause different output for point 1. Point 2 is fixed quite easily (using something like query.getData(row,column)!=null) but point 1 I can't seem to fix. Has anyone come across this? --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
