On 19 July 2011 17:11, Kevin Grittner wrote:
> Tom Lane wrote:
>> "Kevin Grittner" writes:
>>> Josh Berkus wrote:
The timestamp and the timezone in which that timestamp was
entered are two separate pieces of data and *ought* to be in two
separate fields.
>>
>>> So, if you're grab
2008/12/12 David E. Wheeler :
> On Dec 11, 2008, at 3:42 PM, Bruce Momjian wrote:
>
>>> what do you thing about?
>>>
>>> select fce(p1,p2,p3, SET paramname1 = val, paramname2 = val)
>>>
>>> example
>>> select dosome(10,20,30, SET flaga = true, flagb = false)
>>
>> I think AS read more naturally bec
I think array_agg also keeps nulls - although the draft standard I
have seems to contradict itself about this...
Ian
2008/10/26 Jeff Davis <[EMAIL PROTECTED]>:
> Here is a patch to support two aggregate functions:
>
> 1) ARRAY_AGG() -- SQL 2008 standard behavior, returns NULL on no input,
> and s
2008/10/15 Ian Caulfield <[EMAIL PROTECTED]>:
> I started to look at implementing array_agg by making the existing
> intagg stuff more generic
... and here's what I've come up with.
I've currently implemented this as a contrib module to make it quicker
to develop/te
e it should
> be fine.
The right initial state bit is what I was worried about, though I
think I've thought of a way around for now...
> Come to think of it though... Do we require creators of new aggregates own
> the state transition function? If not we have a problem...
No id
2008/10/14 Robert Treat <[EMAIL PROTECTED]>
>
> On Monday 13 October 2008 04:53:44 Markus Wanner wrote:
>
> > Having reviewed the last commit fest's intagg patch as well, I thought
> > we agreed that a more general functionality is wanted for core. But as
> > long as we don't have that, I'd like in
2008/10/11 Hitoshi Harada <[EMAIL PROTECTED]>:
> I am drunk. I forgot cc to -hackers. The talk between me and Ian was like
> that.
>
> 2008/10/12 Hitoshi Harada <[EMAIL PROTECTED]>:
>> 2008/10/12 Ian Caulfield <[EMAIL PROTECTED]>:
>>> 2008/10/11 Hitosh
2008/10/11 Hitoshi Harada <[EMAIL PROTECTED]>
>
> I'm afraid the patch was too huge, trying to send it again without
> attachment...
>
> I made up my mind to scratch former window functions and redesigned
> completely new execution model, based on the discussion with Heikki.
> Attached is the v06
On 17/02/07, Warren Turkal <[EMAIL PROTECTED]> wrote:
PERIOD(INT) is actually listed in the Dr. Snodgrass's book. However, I am not
really sure about the semantics of the type. When would you use a
PERIOD(INT)?
It wouldn't be directly useful for temporal SQL, but I have a number
of tables in a
On 6/10/06, Michael Glaesemann <[EMAIL PROTECTED]> wrote:
Returning to my original example, with a "date_range" type, the tablecould be defined as:
create table teachers__schools_2(teacher text not null, school text not null, period date_range not null, primary key (teacher, schoo
10 matches
Mail list logo
