#2834 closed defect (fixed)
ST_Estimated_Extent and mixedCase table names
Reported by: | pramsey | Owned by: | pramsey |
---|---|---|---|
Priority: | critical | Milestone: | PostGIS 2.1.4 |
Component: | postgis | Version: | 2.1.x |
Keywords: | Cc: | robe |
Description
In 2.0, this worked
select st_estimated_extent('public','BigCountry','geom');
In 2.1 it does not work, but this works
select st_estimated_extent('public','"BigCountry"','geom');
so I accidentally changed the contract when working on the estimation code. Absent anyone complaining, I'd like to revert the behavior to 2.0 behavior so old client code doesn't need to be altered.
Change History (4)
comment:1 by , 10 years ago
comment:3 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
+1 I'm okay with that. I didn't even know the behavior changed so yes Please change back to 2.0 behavior. I consider this a regression bug.