[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [udig-devel] generic geotools datastore support
|
On 23/04/2010, at 10:01 PM, Ugo Taddei wrote:
> Jody Garnett wrote:
>> Yeah progress! Well progress bar; well not say yeah :-P
>
> Progress yes, but progress bar, no. Grey dialogs.
>
>> I am not sure what we should do about progress calculating bounding boxes :-(
>> I have thought of popping up a dialog and asking a user for the bounds if it "takes too long"; but if you have many many tables that will be a trouble. I could try putting off the calculation until you first use the layer ...
>
> I wonder why udig is trying to get the bbox at this point. It should first list the tables, and only get the bbox after I select the tables. But this is probably something coming from geotools.
Bit of both.
uDig want to know the bounds now - so it can cache for later searching. When you search using the search view you have the option to search within the bounds of the current screen.
> FYI: the dialog is still blocked. I'm waiting to see if it'll return before I start my weekend :-)
And this is the part that is in geotools; we are dependent on the implementation provided to return us a good bounds - and many implementations default to scanning the entire table :-(
> I also get loads of
>
> WARNING: No primary key or unique index found for MY_TABLE.
> Apr 23, 2010 11:13:59 AM org.geotools.jdbc.JDBCDataStore getPrimaryKey
>
> But I think/hope this is only a warning.
I think so - it tries to figure out a good "FeatureID" using any primary keys.
Jody
