#1897 closed bug (fixed)
SPIT: Schemas not owned by DB-role cannot be accessed
Reported by: | best | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.0.3 |
Component: | GUI | Version: | 1.1.0 |
Keywords: | SPIT schema rights | Cc: | |
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
When importing shapesfiles with SPIT the user may choose the schema to write the new relation to from a drop-down list. However this list contains only schemas owned by the logged-in database-role.
If the schema is owned by a group role where the logged-in role is a member of it is not listed.
If the logged-in user has create rights on the schema it is not listed either.
To reproduce follow these steps:
- create a schema as role A
- grant create rights to this schema to role B
- start SPIT and log in at the DB as role B
- choose the shape file and see the combo box in column "schema"
Tested with 1.0.1 on WinXP and 1.1.0 on Linux (SUSE 11.1) so I reckon all platforms and versions are affected.
Change History (3)
comment:1 by , 15 years ago
comment:3 by , 15 years ago
@lutra: tested PostGIS Manager this morning, however my users prefer no-overhead plugins :)
@jef: Thanks for fixing!
Hi,
have you tested the postgis manager plugin?
I guess that SPIT is not being developed any more and that postgis manager is the new reference plugin for interacting with postgis.