|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/release-9.0.sgml,v 2.54 2010/08/25 19:41:38 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/release-9.0.sgml,v 2.55 2010/09/01 15:14:42 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <sect1 id="release-9-0">
|
4 | 4 | <title>Release 9.0</title>
|
|
1698 | 1698 | <listitem>
|
1699 | 1699 | <para>
|
1700 | 1700 | Correct calculations of <link
|
1701 |
| - linkend="functions-geometry-op-table"><quote>overlap</quote></link> |
1702 |
| - and <quote>contains</quote> operations over polygons (Teodor Sigaev) |
| 1701 | + linkend="functions-geometry-op-table"><quote>overlaps</quote></link> |
| 1702 | + and <quote>contains</quote> operations for polygons (Teodor Sigaev) |
| 1703 | + </para> |
| 1704 | + |
| 1705 | + <para> |
| 1706 | + The polygon <literal>&&</> (overlaps) operator formerly just |
| 1707 | + checked to see if the two polygons' bounding boxes overlapped. It now |
| 1708 | + does a more correct check. The polygon <literal>@></> and |
| 1709 | + <literal><@</> (contains/contained by) operators formerly checked |
| 1710 | + to see if one polygon's vertexes were all contained in the other; |
| 1711 | + this can wrongly report <quote>true</> for some non-convex polygons. |
| 1712 | + Now they check that all line segments of one polygon are contained in |
| 1713 | + the other. |
1703 | 1714 | </para>
|
1704 | 1715 | </listitem>
|
1705 | 1716 |
|
|