Solutions and work-arounds for most of these problems have been worked out by the community. Ben Nadel created his JSONSerializer.cfc. Coldfusion 11 also added a system for supplying a custom serializer, although I haven't had a chance to try that yet so I don't know if you can avoid all the problems lined out above.
These issues are all very important when using serialized data in javascript or building web services. There is also another issue that comes up when serializing a query and deserializing it back into cf. The data types of the columns are lost. This can be important, as Adam Cameron showed, when trying to do a query of queries on the deserialized query.
Alright that's enough about that, now for the main point of the article. If you are passing data between cf systems, or caching data to be used later on the same system you can use objectsave and objectload.
The code below shows creating a query with varchar and integer columns. Then I save and load the query and show that the data and column types remain intact.
The results of running the code are shown below. First you see the metadata and data for the original query. Then the same thing for the saved and loaded query. Then I show the results of running a query of queries on the loaded query. This returns expected results and does not error when comparing the null value.
This aproach doesn't always work, but when going from cf to cf it avoids all the problems that JSON serialization has.
No comments:
Post a Comment