GeoServer should not require primary keys for oracle/db2
--------------------------------------------------------
Key: GEOS-731
URL: http://jira.codehaus.org/browse/GEOS-731
Project: GeoServer
Issue Type: Bug
Affects Versions: 1.4.0-M2
Reporter: Chris Holmes
Assigned To: Andrea Aime
Priority: Blocker
Fix For: 1.4.0-RC1
See thread: http://www.nabble.com/Oracle-views-disfunctional-with-1.3.4--tf2376356.html
GeoServer on GeoTools 2.1.x did not require primary keys on views. Now if there's not a primary key the default isn't to just use some other field for the fid, or to do some default non-stable id, but it is to completely bomb.
This is bad, we should restore the old behavior, or many more people just won't get things working with GeoServer the first time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira