On Mon, 10 Oct 2005 23:45:03 -0400 (EDT), Bruce Momjian
wrote:
> Oracle has a tendency to keep things around forever, which is nice, but
> over the years it produces a system with lots of strange features that
> make the system hard to use. PostgreSQL has a tendency to remove old,
> unused stuff
[EMAIL PROTECTED] wrote:
> Here is a direct quote from the ORACLE manual:
>
> On most platforms, the concatenation operator is two solid
> vertical bars, as shown in Table 3-3. However, some IBM platforms use
> broken vertical bars for this operator. When moving SQL script files
> between systems
So the argument boils down to we should add concat as a function because
Oracle runs on on EBCDIC and recommends not using concat and because
MySQL has no clue when it comes to SQL standards. Pretty distasteful
arguments, IMHO. Unlike some, I'm in favor of making it easy for people
to migrate from
> -Original Message-
> From: Kevin Grittner [mailto:[EMAIL PROTECTED]
> Sent: 10 October 2005 15:50
> To: [EMAIL PROTECTED]; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #1947: Enhancement Request - CONCAT() function
>
>
> If you are striving for portability, perhaps you are using
No, but Oracle does, which is why I am trying to produce SQL statements that
will run on MySQL, PostgreSQL and Oracle without the need for conversion.
Tony Marston
http://www.tonymarston.net
> -Original Message-
> From: Jim C. Nasby [mailto:[EMAIL PROTECTED]
> Sent: 10 October 2005 1
PostgreSQL runs on machines that use EBCDIC?
On Mon, Oct 10, 2005 at 04:26:15PM +0100, [EMAIL PROTECTED] wrote:
> Here is a direct quote from the ORACLE manual:
>
>
> On most platforms, the concatenation operator is two solid vertical bars, as
> shown in Table 3-3. However, some IBM platforms u
Here is a direct quote from the ORACLE manual:
On most platforms, the concatenation operator is two solid vertical bars, as
shown in Table 3-3. However, some IBM platforms use broken vertical bars for
this operator. When moving SQL script files between systems having different
character sets,
If you are striving for portability, perhaps you are using Java as your
programming language. If so, you could benefit from the fact that the
volunteers in the PostgreSQL community have put the effort into the
JDBC driver to support the escape sequence for portable string
concatenation. This work
Tony Marston wrote:
> > which Oracle supports and MySQL can be made to support via a
> > 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 enou
