Re: Comments on Exclusion Constraints and related datatypes
От | Tom Lane |
---|---|
Тема | Re: Comments on Exclusion Constraints and related datatypes |
Дата | |
Msg-id | 18763.1269267237@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Comments on Exclusion Constraints and related datatypes (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: Comments on Exclusion Constraints and related
datatypes
|
Список | pgsql-hackers |
Simon Riggs <simon@2ndQuadrant.com> writes: > * Exclusion indexes are created with the suffix "_exclusion". That's a > very long suffix and will overflow most defined reports/screens. It > would be much better to use just "_excl", No particular objection here. > * Circles, Boxes and other geometric datatypes defined "overlaps" to > include touching shapes. So > SELECT circle '((0,0), 1)' && circle '((2,0),1)'; > is true, which is fairly strange and makes those datatypes very counter > intuitive. Considering they are instructional aids, this is bad. You're approximately twenty years too late to propose changing that, even if it were clearly a good idea which I doubt. > Also, if the only common sense usage of exclusion constraints is GIST, > why does the syntax default to "btree"? Since your "if" isn't a correct statement, the complaint doesn't follow. regards, tom lane
В списке pgsql-hackers по дате отправления: