[mapguide-internals] MapTips fail when properties have nullvalues?
Paul Spencer
pspencer at dmsolutions.ca
Wed Feb 21 08:48:45 EST 2007
Traian, do you mean that the NULLs should be replaced by empty
strings in the data source (not always feasible/desirable, esp if the
data drives other apps that accomodate the NULL correctly)? or is
there some way to do that in an expression?
Paul
On 20-Feb-07, at 2:39 PM, Traian Stanev wrote:
> I would say it's a bug in the expression evaluation code. Using empty
> string would likely work around the problem.
>
> Traian
>
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason
> Birch
> Sent: Tuesday, February 20, 2007 11:09 AM
> To: MapGuide Internals Mail List
> Subject: RE: [mapguide-internals] MapTips fail when properties have
> nullvalues?
>
> I can't say that I have much insight into why this is happening.
>
> This does mirror expected functionality in most DBMS systems, so it's
> not necessarily a bad thing, but these systems also provide
> functions to
> work around the null values, such as NVL, ISNULL, etc...
>
> Jason
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org
> [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Paul
> Spencer
> Sent: Tuesday, February 20, 2007 05:59
> To: MapGuide Internals Mail List
> Subject: [mapguide-internals] MapTips fail when properties have null
> values?
>
> Hi all ... I filed this as an issue in Trac but I haven't seen any
> comments on it :) Maptips fail to appear when the expression
> references
> a property that is null for the current feature. Another feature that
> does not have null values in the properties will produce a map tip.
>
> Is this behaviour by design or a potential bug? Is there a way to work
> around null values in the data by replacing them with an empty string?
>
>
> Trac ticket is:
>
> http://mapguide.osgeo.org/trac/mapguide/ticket/3
>
> I'm not looking for resolution, just a quick answer on whether this is
> by design, a potential bug, or a configuration problem.
>
> Cheers
>
> Paul
>
> +-----------------------------------------------------------------+
> |Paul Spencer pspencer at dmsolutions.ca |
> +-----------------------------------------------------------------+
> |Chief Technology Officer |
> |DM Solutions Group Inc http://www.dmsolutions.ca/ |
> +-----------------------------------------------------------------+
>
>
>
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>
>
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
+-----------------------------------------------------------------+
|Paul Spencer pspencer at dmsolutions.ca |
+-----------------------------------------------------------------+
|Chief Technology Officer |
|DM Solutions Group Inc http://www.dmsolutions.ca/ |
+-----------------------------------------------------------------+
More information about the mapguide-internals
mailing list