In that case why not make your JSON output represent the sql NULLs as an enumeration or other mapping to the corresponding server side null representation.

For example, if my server side code were C# I would make the JSON objects equal to something like the following:

foo = SqlInt32.Null;



On 9/22/06, Martin Bialasinski <[EMAIL PROTECTED]> wrote:

On 9/22/06, Ryan Gahl <[EMAIL PROTECTED]> wrote:

> Still, don't think it much matters in the end.

It matters when you use null to indicated "not specified". Think SQL.
I convert NULL values to null in JSON output. In that case, you could
not distingish between trailing nulls that were in the original
dataset and nulls that were used to fill the group.






--
Ryan Gahl
Application Development Consultant
Athena Group, Inc.
Inquire: 1-920-954-9798 x2903
Blog: http://www.someElement.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Reply via email to