Re: Position() Bug ? In PostgreSQL 9.2

From: dinesh kumar <dineshkumar02(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Position() Bug ? In PostgreSQL 9.2
Date: 2013-05-02 14:10:39
Message-ID: CALnrH7qNnWCRowOTpsLd6A7S=bncw421_fKiNNWTKMFdr=7+=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Tom,

Thank you very much for the clarification.

Let me set an empty string validation, before passing it to position()
from API.

Thank you once again.

Regards,
Dinesh
manojadinesh.blogspot.com
On 2 May 2013 19:19, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> dinesh kumar <dineshkumar02(at)gmail(dot)com> writes:
> > postgres=# select position('' in 'PostgreSQL'); *// position(Substring as
> > an empty string) is returning 1.*
> > position
> > ----------
> > 1
> > (1 row)
>
> This is correct according to the SQL standard:
>
> <position expression> determines the first position, if any, at
> which one string, S1, occurs within another, S2. If S1 is of
> length
> zero, then it occurs at position 1 (one) for any value of S2. If
> S1
> does not occur in S2, then zero is returned.
>
> regards, tom lane
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Larry Rosenman 2013-05-02 14:50:53 Re: LONG delete with LOTS of FK's
Previous Message Tom Lane 2013-05-02 13:49:38 Re: Position() Bug ? In PostgreSQL 9.2