Re: SQL99 ARRAY support proposal - Mailing list pgsql-hackers

From scott.marlowe
Subject Re: SQL99 ARRAY support proposal
Date
Msg-id Pine.LNX.4.33.0303241114120.23224-100000@css120.ihs.com
Whole thread Raw
In response to Re: SQL99 ARRAY support proposal  (Kevin Brown <kevin@sysexperts.com>)
Responses Re: SQL99 ARRAY support proposal  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
On Sun, 23 Mar 2003, Kevin Brown wrote:

> Joe Conway wrote:
> > Jason Earl wrote:
> > >>Actually, I think it was someone else (Joe???) that is doing the leg
> > >>work, and he was the one choosing explode / implode and getting
> > >>gruff for it, so I was just stepping in and defending his decision.
> > >
> > >Oops, my bad.  My brain must already think that it is the weekend.  My
> > >reasoning still stands, though.  Whoever writes the code gets to pick
> > >the names (assuming, of course, that they can get them past the rest
> > >of the PostgreSQL hackers).
> > 
> > <dons flame proof suit>
> > Yup, that was me. I was watching from the sidelines ;-)
> > 
> > I'll get on with coding and try to consider all of the input when it 
> > comes to picking the names. In the end, it will depend on whatever the 
> > guys with commit access will live with, so I'm not going to worry about 
> > it too much.
> > </dons flame proof suit>
> 
> My 2 cents:
> 
> Use "split" and "merge".  Avoids the "join" issue and avoids the
> "implode/explode" issue too.  :-)

Isn't merge a new SQL keyword in SQL99 or SQL03?



pgsql-hackers by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: [GENERAL] MySQL at .NET conference
Next
From: "scott.marlowe"
Date:
Subject: Re: IO scheduler vs PostgreSQL performance measurement