Hello,
I have installed the new GeoServer 1.7.4 and MySql DataStore Plugin.
Now my currently used Mysql tables have no geometry column in the
FeatureEditor.
The Tables are created with thees statement:
CREATE TABLE IF NOT EXISTS `POLYGONS` (
`ID` int(11) NOT NULL auto_increment,
`NAME` varchar(255) default NULL,
`THE_GEOM` polygon NOT NULL,
PRIMARY KEY (`ID`),
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
The field Name was shown in FeatureEditor, ID is primary and not listed, but
the THE_GEOM field is missed.
I have took the new geoserver-1.7.4-mysql-plugin installed end configured.
The connection is done, only the geometry column is missed.
Has anybody the same problem or a solution for that problem.
Thx 2StepForward
--
View this message in context: http://www.nabble.com/Problems-with-GeoServer-1.7.4-and-MySql-tp23521637p23521637.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hi,
I have test some diverent CREATE TABLES with a spatial column extention but
nothing works.
Has anyone experiences with GeoServer 1.7.4 and MySql or could anyone test
the create definition of mine to exclude a failure of table creation or
spatial definition.
It would be a greate thing,
Cheers 2StepForward
2StepForward wrote:
Hello,
I have installed the new GeoServer 1.7.4 and MySql DataStore Plugin.
Now my currently used Mysql tables have no geometry column in the
FeatureEditor.
The Tables are created with thees statement:
CREATE TABLE IF NOT EXISTS `POLYGONS` (
`ID` int(11) NOT NULL auto_increment,
`NAME` varchar(255) default NULL,
`THE_GEOM` polygon NOT NULL,
PRIMARY KEY (`ID`),
) ENGINE=MyISAM DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
The field Name was shown in FeatureEditor, ID is primary and not listed,
but the THE_GEOM field is missed.
I have took the new geoserver-1.7.4-mysql-plugin installed end configured.
The connection is done, only the geometry column is missed.
Has anybody the same problem or a solution for that problem.
Thx 2StepForward
--
View this message in context: http://www.nabble.com/Problems-with-GeoServer-1.7.4-and-MySql-tp23521637p23523704.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hello,
after spending some times to test the mysql plugin, I have found out that in
my case the spatial column of any table could not detect if there is no
entry in it. If I insert a valid dataset into the table, the FeatureEditor
could detect the column and the right geometry type of it.
But why? I think the column has a defined geometry type in the database
table which could detect in the select quere for the FeatureEditor.
Greetings 2StepForward
2StepForward wrote:
Hi,
I have test some diverent CREATE TABLES with a spatial column extention
but nothing works.
Has anyone experiences with GeoServer 1.7.4 and MySql or could anyone test
the create definition of mine to exclude a failure of table creation or
spatial definition.
It would be a greate thing,
Cheers 2StepForward
--
View this message in context: http://www.nabble.com/Problems-with-GeoServer-1.7.4-and-MySql-tp23521637p23537079.html
Sent from the GeoServer - User mailing list archive at Nabble.com.