Bug report #12391
Postgres character(n) default values not properly handled in attribute form
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: | - | ||
| Category: | Data Provider/PostGIS | ||
| Affected QGIS version: | 2.8.1 | Regression?: | No |
| Operating System: | Easy fix?: | No | |
| Pull Request or Patch supplied: | No | Resolution: | |
| Crashes QGIS or corrupts data: | No | Copied to github as #: | 20565 |
Description
On the OsGeo4W build of QGIS 2.8.1 against PostgreSQL client 8.3.10, table columns defined with fixed-length string data types `char(n)` and `character(n)` that have default values are not properly displayed in the feature creation attribute form. It appears that Postgres internally casts to `bpchar', and that this is being passed literally to the text box. For example, a Postgres column of type `char(6)` with a default value of 'qwerty' will display on the attribute form as 'qwerty'::bpchar
Related issues
Associated revisions
History
#1
Updated by Giovanni Manghi almost 10 years ago
- Category set to Data Provider/PostGIS
#2
Updated by Jürgen Fischer almost 10 years ago
- Status changed from Open to Closed
Fixed in changeset bfb8ab6893d5bf77b4ae92c6c90e0b5b9c7e9ae7.
#3
Updated by Sergio Gollino almost 10 years ago
In the last nightly (2.8.1-42) with PostgreSQL 9.4 the problem persist.
#4
Updated by Jürgen Fischer almost 10 years ago
Sergio Gollino wrote:
In the last nightly (2.8.1-42) with PostgreSQL 9.4 the problem persist.
the fix was applied to master only.