#3329 closed bug (fixed)
Error for postgres's provider when table(statement SELECT ) is outside public's schema
| Reported by: | lmotta | Owned by: | brushtyler |
|---|---|---|---|
| Priority: | minor: annoyance | Milestone: | Version 1.7.0 |
| Component: | Data Provider | Version: | 1.6.0 |
| Keywords: | Cc: | ||
| Must Fix for Release: | No | Platform: | All |
| Platform Version: | Awaiting user input: | no |
Description
When used layers outside public's schema has problem where layer is defined with statement SQL.
The problem is message of error, but, the layer is created correct. Menssage Error: SQL: declare oidcursor binary cursor for select regclass...
The example of layer: dbname='postgis' host=localhost port=5432 user='postgres' key='gid' table="(select l.id AS gid, l.the_geom AS the_geom from gis.tl_20101117_101056_limite l)" (the_geom) sql=
When layer are in public's schema is OK. ... from public.tl_20101117_101056_limite l
Change History (6)
comment:1 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 13 years ago
| Component: | Data Provider → Python plugins and bindings |
|---|---|
| Priority: | major: does not work as expected → minor: annoyance |
comment:3 by , 13 years ago
| Component: | Python plugins and bindings → Data Provider |
|---|---|
| Owner: | changed from to |
| Platform: | Windows → All |
| Status: | assigned → new |
This is a postgres provider's error, not just a plugin one.
comment:4 by , 13 years ago
| Status: | new → assigned |
|---|
comment:6 by , 13 years ago
Just tested it against the 'custom db query' plugin. It's working great. Thanks a lot!
Note:
See TracTickets
for help on using tickets.
Hi, I am the author of this plugin. I am aware of this error message. I haven't found its cause yet, but it seems to have no actual effect on the generation of the layers. I'll keep investigating and report back when I have a fix.