On Thu, Aug 13, 2009 at 12:31:29PM -0400, Dan Halbert wrote:
> Perhaps I should have mentioned that initially.
In retrospect everything is easy!
> SELECT ARRAY[1,2,1+2]::INT[];
> works fine.
I'd not put a cast into that one. I can't see any performance reason
why it's bad, I think it's mainly
From "Sam Mason" :
>The nicer syntax to distinguish things is to use:
>
> TYPENAME 'literal'
Thanks! That is very helpful. I saw that syntax in one example I found on the
web, and incorrectly thought it was an alternate way of writing the function
call.
The point of all this was to figure out
I am trying to make sense of geometric literal syntax in and out of array
syntax. I cannot figure out a general rule: sometimes single quotes work,
sometimes double quotes work, and inside and outside of array literals the
rules are different an seemingly inconsistent.
Examples of all the we
On Thu, Aug 13, 2009 at 11:02:37AM -0400, Dan Halbert wrote:
> I am trying to make sense of geometric literal syntax in and out of
> array syntax. I cannot figure out a general rule: sometimes single
> quotes work, sometimes double quotes work, and inside and outside of
> array literals the rules a
I am trying to make sense of geometric literal syntax in and out of array
syntax. I cannot figure out a general rule: sometimes single quotes work,
sometimes double quotes work, and inside and outside of array literals the
rules are different an seemingly inconsistent.
Examples of all the weird
