Re[2]: [Geoserver-devel] Troubles with PostGIS DataStore???

[Artie K. <a-...@ya...>]

Greetings, Gabriel,

Monday, April 25, 2005, you wrote:

> regarding the patch I comented, my problem was different but may be
> related, I was filtering by a char field with building number. Some of
> them are like ' 002 ' and others have letters too, like ' 002A'. In this
> later case the expression parser was interpreting it as an hexadecimal
> and messing up the filter. This get solved by passing the plain literal
> and letting the feature type get the correct instance type at a later
> instance.

 In fact, now I remember that I had similar problem several times
before. Sometimes dbf files that our GIS department feeds me contain
numeric values in character type columns :) Usually I simply changed
the type of the troublesome attributes to be numeric (fortunately,
they didn't contain any character data). From now on I'll be aware
that there is another solution.
 And question of the ignorant: are features abstracted from their
physical data source so far that it is impossible to obtain type
information for each attribute? This could eliminate the need of
guessing its type from its value or expression applied to it.

> Bu I don't fairly understand what your problem is. Please send the SLD
> and confirm this two features should have the same attribute values.

 I guess there is no need in this now, as all is working pretty fine
after Dave's fixes for JDBCDataStore and lite-renderer. But both
layers, shp and PostGis are identical and I apply identical styles to
them (well, with the exception of letter case in attribute names). I
resort to set of shapefile-based layers in emergency cases, like this
one :)

-- 
WBR,
 Artie