[Geoserver-users] geometry_columns for GeoServer 1.3.-RC2 and GeoServer 1.4.0

GeoServer GeoServer User
1

Hi,

I encountered a scenario which I am not sure of the reason behind it and thus would like to seek some opinions.

We were previously using GeoServer 1.3.0-RC2 and have recently upgraded to GeoServer1.4.0

In the past with 1.3.0-RC2, when we added a new feature type but forgot to include a record for it in the geometry_colum table, we would be prompted with an error message from GeoServer and the creation of the new feature type would fail. However, with 1.4.0, when we also forgot to include a record in the table, there were no messages and the creation would be successful. Our map display will also correctly show the layer for this newly created feature type.

Is this supposed to be reasonable, perhaps due to some enhancement in 1.4.0? If not, then why could this happen and what could be the reason? Would appreciate advice on this. Thanks in advance.

Regards,
Wai See

[This e-mail is confidential and may be priviledged. If you are not the
intended recipient, please kindly notify us immediately and delete the message
from your system; please do not copy or use it for any purpose, nor disclose
its contents to any other person. Thank you.]
---ST Electronics Group---

–
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.410 / Virus Database: 268.17.12/653 - Release Date: 1/26/2007

2

Lee Wai See ha scritto:

Hi,

...

Is this supposed to be reasonable, perhaps due to some enhancement in 1.4.0? If not, then why could this happen and what could be the reason? Would appreciate advice on this. Thanks in advance.

Yeah, the postgis driver was improved a little and now tries to cope
with malformed situations in the database. If I remember properly, if you fail to register stuff in the geometry_columns table, it'll try
to gather info from the first record in your table.
Yet, I would highly suggest to include records in the geometry columns
as well since the SRS cannot be guessed properly otherwise (that's what
I remember, anyways, did not have a look at the actual code).

Cheers
Andrea

3

Andrea Aime wrote:

Yeah, the postgis driver was improved a little and now tries to cope
with malformed situations in the database. If I remember properly, if you fail to register stuff in the geometry_columns table, it'll try
to gather info from the first record in your table.
Yet, I would highly suggest to include records in the geometry columns
as well since the SRS cannot be guessed properly otherwise (that's what
I remember, anyways, did not have a look at the actual code).

The SRID is also extracted from the first feature -- but really, set up your geometry_columns table properly to ensure success.

Cory.