It's not just you. I went to my own specific apps for storing client
variables. EACH variable is in its own column. Works fine.
best, paul
At 06:44 PM 12/30/0
0 -0800, you wrote:
We have several default variables associated client states:
LastVisited,HitCount, etc
So we have two sets of client variable types: custom and allaire's global
set.
After watching the queries on the sql server through the sql profiler, CF
calls two separate queries for each client request. One to the cglobal table
for the global/allaire's variables, and another to cdata for the custom
variables. Even you "disable automatic global variable updates", which
basically renders the global variables useless, CF continues to call two
separate sql statements for each request. I can understand why they would do
this since the client global variables are in the documentation and thus
they should always be there to use but what I don't understand is the lack
of the ability to get rid of that overhead, and it can become a major
overhead considering it's searching on a string key. And why would they use
a string as the search key? Couldn't they just have two int fields, cfid,
cftoken, and group them together as the primary key? I would think the int
search would be faster considering how many times those queries runs a small
improvement can go a long way. And why don't they just use one sql statment
and use join to consolidate the two table rows since they use the same key
instead of the overhead of two separate statements? Is it just me?
Xing
testing 1.2.3...testing 1.2.3...
~ Paid Sponsorship ~
Get Your Own Dedicated Win2K Server! Instant Activation for $99/month w/Free
Setup from SoloServer PIII600 / 128 MB RAM / 20 GB HD / 24/7/365 Tech Support
Visit SoloServer, https://secure.irides.com/clientsetup.cfm.
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
