I ran into this error previously when using Oracle as the backend database for
my layer. As the error suggested, I created a unique index on the view,
republished the layer, and it worked. What database are you using?
In Oracle you can create constraints on views:
Sample from documentation
CREATE VIEW emp_sal (emp_id, last_name,
email UNIQUE,
CONSTRAINT id_pk PRIMARY KEY (emp_id))
AS SELECT employee_id, last_name, email FROM employees;
Donovan
From: Michael Sacauskis [mailto:msacaus...@forwardslope.com]
Sent: Thursday, October 10, 2013 10:25 AM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] No primary key or unique index found for
I'm getting the following error "23:38:06,673 WARN [org.geotools.jdbc] (MSC
service thread 1-2) No primary key or unique index found for tcwradiuscf". The
error is occurring on a view. We're using version 2.2.4.
Any help would be greatly appreciated.
Mike
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
