"David G. Johnston" writes:
> On Sun, Aug 18, 2019 at 8:53 AM PG Doc comments form
>> Noticed strange thin with @>
>> Query "select '{1,2}'::int[] @> '{1,2,2,2,2,2,2,2}'::int[]" returns true,
>> but first array contains even l
Query "select '{1,2}'::int[] @> '{1,2,2,2,2,2,2,2}'::int[]" returns true,
> but first array contains even less elements then second.
> I think it's a bug in "contains" logic, but don't know where to submit it.
>
Its a valid interpretation of "cont
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/functions-array.html
Description:
Hi.
Noticed strange thin with @>
Query "select '{1,2}'::int[] @> '{1,2,2,2,2,2,2,2}'::int[]" returns true,
but fir
On Tue, Apr 9, 2019 at 3:03 PM Jind?ich Vavru?ka
wrote:
> Dear Tom, it works only in psql, it does not work when you talk to the
> server using postgresql protocol. That is my point.
>
> e.g. in the following code the query causes Syntax error (see the text in
> red). That means it does not work.
ame, startUtc, endUtc, format]
).then( result => { if( result.rowCount > 0 ) { return
result.rows[0].contest_key } else { return undefined; } });
}
...
}
-Original Message-
From: Tom Lane
Sent: Tuesday, April 9, 2019 5:57 PM
To: jindr...@vavruska.cz
C
PG Doc comments form writes:
> QUOTE:
> The CAST() syntax conforms to SQL. The type 'string' syntax is a
> generalization of the standard: SQL specifies this syntax only for a few
> data types, but PostgreSQL allows it for all types. The syntax with :: is
> historical PostgreSQL usage, as is the f
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/11/sql-syntax-lexical.html
Description:
QUOTE:
The CAST() syntax conforms to SQL. The type 'string' syntax is a
generalization of the standard: SQL specifies this syntax only for a few
data t
