PostGIS - fixed columns lengths when using prepared statements
Description
When configuring postgis plugin with
("preparedStatements", true)
fixed column lengths (255) will be created in the DB schema for strings (char varying (255)) which causes a problem if the contents to be inserted are longer. If not using prepared statements the length isn't limited and there is no problem. The cause for this behaviour is that there is a seperate dialect for prepared staments (PostGISPSDialect) which doesn't override method getDefaultVarcharSize with should return -1 like the PostGISDialect.
When configuring postgis plugin with
("preparedStatements", true)
fixed column lengths (255) will be created in the DB schema for strings (char varying (255)) which causes a problem if the contents to be inserted are longer. If not using prepared statements the length isn't limited and there is no problem.
The cause for this behaviour is that there is a seperate dialect for prepared staments (PostGISPSDialect) which doesn't override method getDefaultVarcharSize with should return -1 like the PostGISDialect.
I could provide a fix for that issue.