ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

coldfusion: All content tagged as coldfusion in NoSQL databases and polyglot persistence

ColdFusion's Flawed JSON and NoSQL databases

It’s kind of difficult to understand why they cannot get JSON right:

Now the surprise: ColdFusion 9.0.1 says goodbye to the number format in JSON. All numbers in JSON will become strings once ColdFusion gets its hand on the data. There are no more numbers. 10 becomes “10”, 10.2 becomes “10.2” etc. Even though the patch notes stated that differently. And i still believe it was not Adobe’s intention to remove numbers but somehow this flawed implementation slipped in.

As the author puts it:

ColdFusion 9.0.1 is essentially disqualified to be used with NoSQL datastores where JSON is involved.

via: http://coldfusion.tcs.de/adobe-please-fix-coldfusion-serializejson/