On 2010-04-30, silly sad wrote:
> suppose i request
>
> SELECT foo(t.x) FROM t LIMIT 1;
>
> Whither it DEFINED how many times foo() will be executed?
foo will be executed repeatedly until it returns a result or all the
rows in t are exhausted.
> May anyone rely on it?
not sure
> Or we have to
On 04/30/2010 06:20 PM, silly sad wrote:
suppose i request
SELECT foo(t.x) FROM t LIMIT 1;
Whither it DEFINED how many times foo() will be executed?
May anyone rely on it?
Or we have to avoid this non SQLish trick?
It will execute foo only once, and give only one row out of the n rows
it r
suppose i request
SELECT foo(t.x) FROM t LIMIT 1;
Whither it DEFINED how many times foo() will be executed?
May anyone rely on it?
Or we have to avoid this non SQLish trick?
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresq
On 2010-04-29, Justin Graf wrote:
> I'm pretty sure this is the regualr expression to find all non ASCII=20
> chars.. [^\x00-\xFF]
Not in postgres.
\x00 does not work well in strings, and \xFF is invalid utf-8.
this is why I used char()
(also ASCII is undefined past at \x7F ... but the or
On 2010-04-29, Andreas wrote:
> Hi,
>
> while writing the reply below I found it sounds like beeing OT but it's
> actually not.
> I just need a way to check if a collumn contains values that CAN NOT be
> converted from Utf8 to Latin1.
> I tried:
> Select convert_to (my_column::text, 'LATIN1') fr
