Bug report #2016
PgQuery 0.1.1 : output schema not took into account
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Low | ||
| Assignee: |  Borys Jurgiel | ||
| Category: | Python plugins | ||
| Affected QGIS version: | Regression?: | No | |
| Operating System: | Windows | Easy fix?: | No |
| Pull Request or Patch supplied: | Resolution: | invalid | |
| Crashes QGIS or corrupts data: | Copied to github as #: | 12076 |
Description
In english:
In PgQuery for QGIS version 0.1.1, when the "temporary" table is created, it is created in the "public" schema whatever "output schema" is filled. This table is however loaded thereafter with the "good" specified schema. Table creation should take UI "output schema" into account ! Thanks.
--
In French:
Dans PgQuery for QGIS version 0.1.1, lorsque la table "temporaire" est crée, elle l'est dans le schéma public quel que soit le "output schema" indiqué. Par contre le programme tente bien de la lire dans le schéma spécifié. La création de table doit prendre en compte "l'output schema". Merci !
History
#1
Updated by Jürgen Fischer almost 15 years ago
- Resolution set to invalid
- Status changed from Open to Closed
please report this to the plugin author. This TRAC is for QGIS and core plugins.
#2
Updated by Borys Jurgiel almost 15 years ago
I've just passed this reequest to the author.