|
|
Hans Yperman created an issue |
|
Feature type customization clashes with database fields with special characters |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.21.1 |
|
Assignee: |
Unassigned |
|
Created: |
03/Oct/22 4:43 PM |
|
Environment: |
While upgrading to geoserver 2.21.1, we find that geoserver does not accept some field names in our database. We can work around it by disabling the attibute customizer. When enabling the customizer, it drops “double quotes” around these field names in the source column, but that does not seem to help. Also strange: Some parts of the code expect a CQL expression in source, other an XPath (see SimpleFeaturePropertyAccessorFactory :: SimpleFeaturePropertyAccessor.get ). Hence, I tried and failed to use xpath syntax for the field names. Some examples of database field names that won’t work: $code (dollar at start), 12data (number at start),detection-date (minus makes it seem like 2 expressions), added in (contains a space). |
|
Priority: |
|
|
Reporter: |
Medium|
|
|
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100207-sha1:bddf6e1) |
|
|
|
