[mapguide-internals] Re: FeatureSet xml serialization issues (RE: SELECTFEATURES via mapagent and null values)

[Zac Spitzer]

being a web based project, this doesn't really translate very to the web

it's a pretty common approach to treat nulls as empty strings in web
development, i understand how it makes more sense in lower level
programing, but with the web it's a bit different

nulls as empty strings translates perfectly to xml, web forms, urls etc

I can't see how you can cleanly support anything else without a lot
of ugly workarounds.

So where in mapguide does an empty string get interpreted differently
than a null value?

With FDO it's just a convention between different databases right?

z

On 9 April 2010 11:41, Jackie Ng <jumpinjackie at gmail.com> wrote:
>
> An empty string (a string property whose value is "") is different to a null
> string (a string property without an actual assigned value).
>
> If by your suggestion that null property values are coerced into empty
> strings when serializing, then empty string values (which may be legitimate)
> will be misinterpreted as null string values when serialized.
>
> - Jackie
> --
> View this message in context: http://n2.nabble.com/SELECTFEATURES-via-mapagent-and-null-values-tp1822076p4874876.html
> Sent from the MapGuide Internals mailing list archive at Nabble.com.
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168