From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
---|---|
To: | jonathan(dot)katz(at)excoventures(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #8813: Clarifying OVERLAPS in the Docs |
Date: | 2014-01-13 13:18:48 |
Message-ID: | 52D3E7B8.6040705@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 01/13/2014 06:25 AM, jonathan(dot)katz(at)excoventures(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8813
> Logged by: Jonathan S. Katz
> Email address: jonathan(dot)katz(at)excoventures(dot)com
> PostgreSQL version: 9.3.2
> Operating system: N/A
> Description:
>
> This was reported by Adam Mackler (mackler) in the doc comments, and am
> relaying this. My edits are in []
>
> ========
>
> Section 9.9 (v. 9.3 manual) says "the SQL OVERLAPS operator is supported."
>
> There is no entry in the [documentation] index for "OVERLAPS." I've been
> operating for some time now on the mistaken assumption that OVERLAPS was not
> supported, simply because I assumed that if it were, then there would be an
> index entry for it.
>
> I propose modifying the [documentation] index by adding an "OVERLAPS" entry.
Added.
I tried to make the link from the index point to the right paragraph,
but couldn't figure out how to do that. So now it just points to the
whole Date/Time Functions and Operators section, and you have to scroll
to find the OVERLAPS paragraph. But at least iẗ́'s in the index now.
- Heikki
From | Date | Subject | |
---|---|---|---|
Next Message | mmogadime | 2014-01-13 14:46:20 | BUG #8822: What's the work around for the following exception? |
Previous Message | Alvaro Herrera | 2014-01-13 12:59:36 | Re: BUG #8757: Dublicate rows, broken primary key. |