Opened 19 years ago
Closed 15 years ago
#962 closed defect (fixed)
Postgresql field count wrong
Reported by: | Owned by: | warmerdam | |
---|---|---|---|
Priority: | high | Milestone: | 1.6.1 |
Component: | OGR_SF | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description
Load tiger data into schema A in a postgres database. Load tiger data into schema B in a postgres database. The next time ogr connect to postgresql it will double the number of fields for each table - say entitynames. The right solution is for each Postgresql layer know which schema it belongs to and then add that to the SELECT statement at line 271 of ogrpgtablelayer. The quick hack solution is to add DISTINCT to the select statement. I have checked the quick hack in.
Change History (1)
comment:1 by , 15 years ago
Milestone: | → 1.6.1 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The described issue has probably be fixed since a few releases, but when actually trying to test it, I discovered there was a remaining bug somehow related to that.
Fixed in trunk in r16119, in branches/1.6 in r16120 and test adjusted in r16121