Received: from spelunker.keyway.net (spelunker.keyway.net [207.155.50.41]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA94917 for ; Sun, 10 Oct 1999 01:05:45 -0400 (EDT) (envelope-from doug.t@deltanet.com) Received: from deltanet.com (b155-49-stat-101.keyway.net [207.155.49.101]) by spelunker.keyway.net (8.9.3/8.9.3) with ESMTP id WAA24335; Sat, 9 Oct 1999 22:04:01 -0700 (PDT) Message-ID: <38001E65.8155F291@deltanet.com> Date: Sat, 09 Oct 1999 22:04:38 -0700 From: Doug Thistlethwaite X-Mailer: Mozilla 4.5 [en]C-CCK-MCD compaq (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Herouth Maoz CC: pgsql-sql@postgreSQL.org, jens@jens.de Subject: Re: [SQL] combining columns in select References: from Jens Glaser at "Oct 1, 1999 09:20:31 pm" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit What I was trying to do is develop a java application using the ODBC and then move it to postgres & a linux database when I had everything working. Unfortunately, I have discovered that there are many differences in the "standard SQL" that each driver uses. I could not find any ODBC drivers that us local data that allow the "||" concatenation symbol. Most of them use the "+" symbol. I have found the same problem with "Memo" vs "text" fields as well. The ODBC driver for dbase (the one which seems to work best in my case) also uses the # symbol for dates while postgres likes the ' symbol. I guess I have to live with this and write separate query statements for each implementation. Doug Herouth Maoz wrote: > At 03:15 +0200 on 03/10/1999, "D'Arcy" "J.M." Cain wrote: > > > While you are correct in your solution, it isn't a parser bug. It just > > follows the spec. There has been talk of allowing the first form as > > an extension. > > Since when has "+" become the string concatenation operator? It used to be > "||" last time I checked. > > Herouth > > -- > Herouth Maoz, Internet developer. > Open University of Israel - Telem project > http://telem.openu.ac.il/~herutma