Hi,

We are automating layer creation through the REST API and part of our
design involves randomly generated layer names.  We ran into an issue where
it seems that GeoServer stores layer names in a 64 char length field which
is too small for our current purposes.  Is there a way to adjust the size
of this field without hacking into the src?

[INFO] [talledLocalContainer] Caused by: org.h2.jdbc.JdbcSQLException:
Value too long for column LAYER_NAME VARCHAR(64):
'geodashboard:lxshrv7h0g0izi49dviqtj1mjy4wrds6rscs9lsb4hx9m41yuvj3sz80midx6f7'
(76); SQL statement:

...
[INFO] [talledLocalContainer] INSERT INTO TILESET select ?, ?, ?, ?, ?, 0
 WHERE NOT EXISTS(SELECT 1 FROM TILESET WHERE KEY = ?) [90005-119]; nested
exception is org.h2.jdbc.JdbcSQLException: Value too long for column
LAYER_NAME VARCHAR(64):
'geodashboard:lxshrv7h0g0izi49dviqtj1mjy4wrds6rscs9lsb4hx9m41yuvj3sz80midx6f7'
(76); SQL statement:
[INFO] [talledLocalContainer] INSERT INTO TILESET select ?, ?, ?, ?, ?, 0
 WHERE NOT EXISTS(SELECT 1 FROM TILESET WHERE KEY = ?) [90005-119]
[


*Justin*

<http://www.linkedin.com/pub/justin-lewis/b/b94/861/>
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to