[Geoserver-users] Problem with CQL datatype string in PostGIS

Jorge_Samuel_Mendes · October 28, 2015, 8:56am

Hi to all

I am trying to set a WFS with complex Features, I am running the app-schema on a postgis 9.3 using geoverser 2.7.3 (postgresql-8.4-701.jdbc3.jar)

I am accessing a table and want to use a concatenate string function to generate the gmlD example:

datastore soil soil:SO_Soil soil:SO_Soil **strConcat('so_' , profile_id)**

And I get the following error:

java.lang.IllegalArgumentException: Filter Function problem for function strConcat argument #1 - expected type String
Filter Function problem for function strConcat argument #1 - expected type String

profile_id is the column name in table soil
I saw some examples with strConCat instead of strConcat, but it seems that there is no difference
OK, the profile_id needs to be a string, I have change the column datatype in the DB from integer to text, and had the same error, and now to character varying(10) and stll the same error
Have you tried to turn geoserver/postgis off and on??? Yes I have done it

Any suggestion of what might be wrong? Do I need to cast profile_id to string type ???

Thank you

···

-- 
ISRIC - World Soil Information 
Post: PO box 353, 6700 AJ, Wageningen,
The Netherlands Visiting Address: Droevendaalsesteeg 3, 6708 PB
Wageningen (Bdg. 101), 
Office: C.013 
Office Phone: +31 (0) 317 4 83715
Mobile Phone: +31 (0) 613 9 06950
Skype: jorge.de.jesus (Jorge Samuel Mendes de Jesus) 
OpenPGPKey: 0xA3D0065A

Jorge_Samuel_Mendes · October 28, 2015, 9:54am

Hi

I managed to solve it. The column: profile_id

Is a primary key in a table, and my datastorage defintion was like this:

datastore

dbtypepostgisng

The expose primary key was missing and therefore the default was:false (no profile_id ) therefore the strConcat couldnt work without the input column

So:
Expose primary keystrue

J.

···

On 28-10-15 09:56, Jorge Samuel Mendes de Jesus wrote:

Hi to all

I am trying to set a WFS with complex Features, I am running the app-schema on a postgis 9.3 using geoverser 2.7.3 (postgresql-8.4-701.jdbc3.jar)

I am accessing a table and want to use a concatenate string function to generate the gmlD example:
datastore soil soil:SO_Soil soil:SO_Soil **strConcat('so_' , profile_id)**
And I get the following error:

java.lang.IllegalArgumentException: Filter Function problem for function strConcat argument #1 - expected type String
Filter Function problem for function strConcat argument #1 - expected type String

profile_id is the column name in table soil

I saw some examples with strConCat instead of strConcat, but it seems that there is no difference

OK, the profile_id needs to be a string, I have change the column datatype in the DB from integer to text, and had the same error, and now to character varying(10) and stll the same error

Have you tried to turn geoserver/postgis off and on??? Yes I have done it

Any suggestion of what might be wrong? Do I need to cast profile_id to string type ???

Thank you

-- 
ISRIC - World Soil Information 
Post: PO box 353, 6700 AJ, Wageningen,
The Netherlands Visiting Address: Droevendaalsesteeg 3, 6708 PB
Wageningen (Bdg. 101), 
Office: C.013 
Office Phone: +31 (0) 317 4 83715
Mobile Phone: +31 (0) 613 9 06950
Skype: jorge.de.jesus (Jorge Samuel Mendes de Jesus) 
OpenPGPKey: 0xA3D0065A

-- 
ISRIC - World Soil Information 
Post: PO box 353, 6700 AJ, Wageningen,
The Netherlands Visiting Address: Droevendaalsesteeg 3, 6708 PB
Wageningen (Bdg. 101), 
Office: C.013 
Office Phone: +31 (0) 317 4 83715
Mobile Phone: +31 (0) 613 9 06950
Skype: jorge.de.jesus (Jorge Samuel Mendes de Jesus) 
OpenPGPKey: 0xA3D0065A

Stefano_Costa3 · October 28, 2015, 10:10am

Hi Jorge,
please read my comments below.

···

On Wed, Oct 28, 2015 at 9:56 AM, Jorge Samuel Mendes de Jesus <jorge.mendesdejesus@anonymised.com…> wrote:

I am trying to set a WFS with complex Features, I am running the app-schema on a postgis 9.3 using geoverser 2.7.3 (postgresql-8.4-701.jdbc3.jar)

I’m working with the same stuff. Are you on Windows or Linux or Mac?

I am accessing a table and want to use a concatenate string function to generate the gmlD example:
datastore soil soil:SO_Soil soil:SO_Soil **strConcat('so_' , profile_id)**
And I get the following error:

java.lang.IllegalArgumentException: Filter Function problem for function strConcat argument #1 - expected type String
Filter Function problem for function strConcat argument #1 - expected type String

Is this the only mapping using a strConcat function (BTW, it’s strConcat, not strConCat)? The mapping looks ok to me.

profile_id is the column name in table soil

I saw some examples with strConCat instead of strConcat, but it seems that there is no difference

OK, the profile_id needs to be a string, I have change the column datatype in the DB from integer to text, and had the same error, and now to character varying(10) and stll the same error

Have you tried to turn geoserver/postgis off and on??? Yes I have done it

It works for me, regardless of the type of the column, i.e. it works both with an integer column and with a character varying column. I didn’t try with a text column, but I’d expect it to work with that too.

Any suggestion of what might be wrong? Do I need to cast profile_id to string type ???

No idea, you mapping looks correct. Could you post a dump of your DB with minimal data and specify the XML schema you’re targeting, so I can try to reproduce the issue?

–

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts! Visit
[http://goo.gl/it488V](http://goo.gl/it488V) for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:     +39 0584 1660272

[http://www.geo-solutions.it](http://www.geo-solutions.it)
[http://twitter.com/geosolutions_it](http://twitter.com/geosolutions_it)

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility  for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.

Stefano_Costa3 · October 28, 2015, 10:20am

Ah, right, I was bit by this in the past, but it had not occurred to me reading your e-mail.

Glad you figured it out.

···

On Wed, Oct 28, 2015 at 10:54 AM, Jorge Samuel Mendes de Jesus <jorge.mendesdejesus@anonymised.com> wrote:

Hi

I managed to solve it. The column: profile_id

Is a primary key in a table, and my datastorage defintion was like this:

datastore

dbtypepostgisng

The expose primary key was missing and therefore the default was:false (no profile_id ) therefore the strConcat couldnt work without the input column

So:
Expose primary keystrue

–

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts! Visit
[http://goo.gl/it488V](http://goo.gl/it488V) for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax:     +39 0584 1660272

[http://www.geo-solutions.it](http://www.geo-solutions.it)
[http://twitter.com/geosolutions_it](http://twitter.com/geosolutions_it)

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility  for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.