> -----Original Message-----
> From: David Fetter [mailto:david@fetter.org]=20
> Sent: 08 October 2005 22:16
> To: Tony Marston
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1947: Enhancement Request - CONCAT() function
>=20
>=20
> On Sat, Oct 08, 2005 at 12:39:40PM +0100, Tony Marston wrote:
> >=20
> > The following bug has been logged online:
> >=20
> > Bug reference: 1947
> > Logged by: Tony Marston
> > Email address: tony@marston-home.demon.co.uk
> > PostgreSQL version: 8.0.3
> > Operating system: Windows XP
> > Description: Enhancement Request - CONCAT() function
> > Details:
> >=20
> > I would like the option to use CONCAT(field1, ' ', field2)=20
> instead of=20
> > the vertical bar syntax (field1 || ' ' || field2) as this is also=20
> > available in other popular databases (MySQL, ORACLE). I am=20
> trying to=20
> > develop applications which are daabase independent, so the use of=20
> > common SQL syntax is very important.
>=20
> Fix your application so that it uses the SQL standard ||,=20
Not until you fix your product so that it follows the current SQL standard
TO THE LETTER and contains NOTHING which is not in the standard!
It is a well-known fact that every database vendor includes their own
"extensions" to the SQL standard simply because they want to offer more
functionality to their users, and they can't wait for it to be formally
documented in the standard. It is also a well known fact that extensions
made by one database vendor may also be adopted by other vendors in order to
maintain a level of compatibility.
Are you honestly going to tell me that if your user base requested certain
additional functionality that you would refuse to include it simply because
it was "not in the standard"? If every database vendor offered nothing but
the SQL standard there would be nothing to differentiate between them, so
you would not be able to say "ou daabas is better than theirs beause..."
> which Oracle supports and MySQL can be made to support via a=20
> runtime option.
They also both support CONCAT() because there are sometimes difficulties in
dealing with vertical bars in the character sets used by certain operating
systems and file systems. If enough database vendors offer it then it becmes
a "de facto" standard.
Tony Marston
http://www.tonymarston.net=20