Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#513 closed enhancement (fixed)

Can't upload dbf only with gui (without unchecking index?)

Reported by: robe Owned by: pramsey
Priority: medium Milestone: PostGIS 1.5.2
Component: postgis Version: 1.5.X
Keywords: Cc:


I have a table that just has attribute data (no geom). Everything goes fine and well until it tries to create an index.

Failed SQL begins: "CREATE INDEX "parcel_10_data_the_geom_gist" ON "scratch"."parcel_10_data" using gist ("the_geom" gist_geometry_ops);

I haven't tried reloading yet, but I suspect it will work if I uncheck the "CREATE INDEX" checkbox.

I suppose it may be too much to ask, but can we have the gui not try to create an index if there is no geometry to index even if the user is not smart enough to uncheck the "CREATE INDEX" option.

Change History (6)

comment:1 by robe, 14 years ago

To add to this what makes loading dbf only cumbersome.

In the mask section — we have only .shp and it automatically filters to that when you first load the browse. Can we add .dbf to that filter.

Right now to load a dbf file that has no corresponding shp, I have to 1) browse to a shp file and select 2) Rebrowse and then pick the dbf (strangely going in a second time to browse there is no filter set) so I am able to do this.

But as you can see the process is a bit convoluted.

comment:2 by pramsey, 14 years ago

Actual issue should be fixed at r5950.

comment:3 by robe, 14 years ago

Milestone: PostGIS 1.5.2PostGIS 1.5.3

Better but still problematic in that the .shp is the only thing that shows. So still cumbersome (if only a user could guess what to do — browse to an shp file /cancel then go back and browse again).

comment:4 by pramsey, 14 years ago

Added a dbf filter at r5977. Not sure how good/smart this is, because now a whole subsidiary branch of behaviour is opened up. If I open a dbf file, should the options now automatically default to "load dbf only", etc, etc, etc. Basically the GUI starts to get really hairy with side effects.

comment:5 by robe, 14 years ago

Resolution: fixed
Status: newclosed

As I recall the commandline doesn't care if a dbf extension, .shp or no extension is given. It will load the shp unless an explicit dbf-only command is given or there is no accompanying shp. The gui should behave the same way to be consistent.

Anyrate I think its fine the way you have it as long as the .shp is the default filter.

At some point we should add a dbf only option checkbox like the commandline has but that is a task for another day.

comment:6 by robe, 14 years ago

Milestone: PostGIS 1.5.3PostGIS 1.5.2
Note: See TracTickets for help on using tickets.