> Someone correct me if I am wrong, but if you enable "non-latin" text for a
> datasource, cfqueryparam will treat ALL
> cf_sql_varchar data as unicode. Meaning there is no way to specify a
> non-unicode (ansi) string other than to NOT use
> cfqueryparam?
I believe this is correct. At least with MS SQL Server, I believe this
is correct. I don't know enough about other platforms to say.
> I'm trying to weigh the value of enabling the "non-latin" option versus the
> "N" hinting, but I can't find a way to enter
> single-byte strings with cfqueryparam once the option is checked, and I think
> it's silly to sacrifice 50% of my storage
> space for this convenience.
Storage space is cheap. That said, if you want to use Unicode in some
fields/tables but not others, you could simply create two separate
datasources, one with Unicode enabled and one without.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/
Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on
GSA Schedule, and provides the highest caliber vendor-authorized
instruction at our training centers, online, or onsite.
~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:335709
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
