Client Variables in different case

[craigpatrickbenner]

We are using ColdFusion 5 and ColdFusion MX 6.1 in production use where 5 are
the main server and version 6.1 are used for very specific events. Anyways we
use client variables to manage are state and login information. We are
noticing that once 6.1 uses the variables it converts them to lowercase, so
when the user browses back over to the 5.0 server it can't find any of the
client variables (it uses upper case). Has anyone else had this issue? And
does anyone know if Macromedia is aware of this change. Can anyone think of a
work around or a setting somewhere ot change the case sensitivity?

[byron1021]

I wouldn't imagine that the case in the database would be causing an issue,
unless the database or database driver is case sensitive. This isn't the case
for MS SQL Server or the driver in CFMX or CF5. I'm not sure about other
databases though. I think MySQL can be case sensitive. Now that I think
about it, I think there is a way in MS SQL Server to set a database to case
sensitive or something like that. Maybe that's a function that does case
sensitive comparison. I can't remember. Maybe this is something to look into.

[craigpatrickbenner]

it has nothing to do with the database case sensetivity, CF only queries the
data based on the CFID and CFTOKEN column, therefore returning the "data"
column.

i can show an example of data that when I am on the machine with CF 5 running
the data looks like the following

#LOGGEDIN=1#.....

then I jump to the CF 6 box and ALL the data changes to lower case (like the
following)

#loggedin=1#.....

then I jump back to CF 5 box and i get duplicate data one lower, one upper

#loggedin=1#LOGGEDIN=0#

PS. i recieved the following response from houseoffusion.com
i hope a macromedia developer reads this and says OH CRAP that should of been
fixed, instead of non-issue.
-------------------------------------------------------------
Don't use the same tables for CFMX and CF5/CF4.x/etc.

I opened bug 37574 in 2002 for this and a CF Engineer closed it as a
non-issue, i.e. don't do that.

My description was:

"Client management CDATA and CGLOBAL tables are written to with
different styles and conflict when shared by CF5 and Neo. When CF5 and
Neo are running the same application concurrently and when using the
same shared CDATA and CGLOBAL tables in a dsn, Neo will always overwrite

the CF5 CDATA.data column and the CGLOBAL.data column. CF5 will always
add its own entries to both of these fields IN ADDITION to those already

there from Neo, where Neo had lowercase name value pairs and CF5 added
uppercase name value pairs. Interestingly, sometimes Neo inserts the
value of CFTOKEN without the name/value pair format where it omits the
name but writes the data. For example the CDATA.data field might start
with "=12345678#foo=bar#" where the the =12345678 is missing the left
side."