incompatible. They might be really similar, but they're different enough to
pretty much break everything. I think you're going to have to change your
code throughout, or perhaps write a custom serialization routine that mimics
the CF5 serialization.
Cheers,
barneyb
> -----Original Message-----
> From: Scott Brady [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 10, 2004 2:05 PM
> To: CF-Talk
> Subject: WDDX, CFMX, and NULLs
>
> I managed to figure out how to fix our client variable
> problem with MX/Oracle (we're going to have to drop and
> rebuild the cdata and cglobal tables in the database), but am
> running into WDDX problems for converting from CF5 to MX6.1
> and, again, can't find anything online.
>
> So, here's our issue.
>
> We have a query in one frame that loads data, some of which
> can be null. We send it to another frame as JS WDDX data and
> go from there. However, the null data, instead of being
> converted to an empty string ('') [as it does in CF5], it
> goes through as null, which causes problems in our JS code
> where we check the length of a column.
>
> Aside from searching through all of our code and changing it
> to take this into account, is there some other fix someone
> can suggest? We use this a lot and it will be a very
> extensive change.
>
> Thanks!
>
> Scott
>
> ---------------------------
> Scott Brady
> http://www.scottbrady.net/
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
