Skip site navigation (1) Skip section navigation (2)

Re: BUG #1947: Enhancement Request - CONCAT() function

From: Chris Travers <chris(at)travelamericas(dot)com>
To: Tony Marston <tony(at)marston-home(dot)demon(dot)co(dot)uk>
Cc: "'Jim C(dot) Nasby'" <jnasby(at)pervasive(dot)com>,'Bruce Momjian' <pgman(at)candle(dot)pha(dot)pa(dot)us>,'David Fetter' <david(at)fetter(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1947: Enhancement Request - CONCAT() function
Date: 2005-10-20 17:16:40
Message-ID: 4357D0F8.9050909@travelamericas.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Tony Marston wrote:

>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.
>  
>
Hi Tony,

Let me make a constructive suggestion.  I see what you are trying to do 
and I can understand why this is useful.  However, I agree with the main 
individuals here that it should not be a part of the core project.  
Fortunately PostgreSQL is extensible and it is quite easy to release 
custom extensions that can make these things happen without messing with 
the core project.

One of the things I am going to be doing is creating either a Perl 
(client) or PLPGSQL (server) function to create concat() functions with 
up to x number of arguments.  This will be used as part of our 
server-side porting framework to allow for easier migration from MySQL 
in particular.

Would you be interested in participating in/testing/contributing to such 
a project?

Best Wishes,
Chris Travers
Metatron Technology Consulting

>Tony Marston
>
>http://www.tonymarston.net 
>
>
>
>  
>
>>-----Original Message-----
>>From: Jim C. Nasby [mailto:jnasby(at)pervasive(dot)com] 
>>Sent: 10 October 2005 18:19
>>To: tony(at)marston-home(dot)demon(dot)co(dot)uk
>>Cc: Bruce Momjian; 'David Fetter'; pgsql-bugs(at)postgresql(dot)org
>>Subject: Re: [BUGS] BUG #1947: Enhancement Request - CONCAT() function
>>
>>
>>PostgreSQL runs on machines that use EBCDIC?
>>
>>On Mon, Oct 10, 2005 at 04:26:15PM +0100, 
>>tony(at)marston-home(dot)demon(dot)co(dot)uk wrote:
>>    
>>
>>>Here is a direct quote from the ORACLE manual:
>>>
>>><quote>
>>>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, such as between ASCII and 
>>>EBCDIC, vertical bars might not be translated into the vertical bar 
>>>required by the target Oracle environment. Oracle provides 
>>>      
>>>
>>the CONCAT 
>>    
>>
>>>character function as an alternative to the vertical bar 
>>>      
>>>
>>operator for 
>>    
>>
>>>cases when it is difficult or impossible to control translation 
>>>performed by operating system or network utilities. Use 
>>>      
>>>
>>this function 
>>    
>>
>>>in applications that will be moved between environments 
>>>      
>>>
>>with differing 
>>    
>>
>>>character sets. </quote>
>>>
>>>Tony Marston
>>>http://www.tonymarston.net
>>>
>>>pgman(at)candle(dot)pha(dot)pa(dot)us wrote:
>>>      
>>>
>>>>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 enough 
>>>>>database vendors offer it then it becmes a "de facto" standard.
>>>>>          
>>>>>
>>>>I have never heard of problems with vertical bars in any of those 
>>>>settings.  Can you elaborate?  I don't see how operating 
>>>>        
>>>>
>>systems and 
>>    
>>
>>>>file system character sets relate to SQL query characters.
>>>>
>>>>-- 
>>>>  Bruce Momjian                        |  http://candle.pha.pa.us
>>>>  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
>>>>  +  If your life is a hard drive,     |  13 Roberts Road
>>>>  +  Christ can be your backup.        |  Newtown Square, 
>>>>        
>>>>
>>Pennsylvania 19073
>>    
>>
>>>---------------------------(end of 
>>>broadcast)---------------------------
>>>TIP 5: don't forget to increase your free space map settings
>>>
>>>      
>>>
>>-- 
>>Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
>>Pervasive Software      http://pervasive.com    work: 512-231-6117
>>vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461
>>
>>    
>>
>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>
>
>  
>


In response to

pgsql-bugs by date

Next:From: Jean-Pierre PelletierDate: 2005-10-20 19:53:09
Subject: function currval(character varying) does not exist, PostgreSQL 8.1 beta3
Previous:From: Chris TraversDate: 2005-10-20 17:07:18
Subject: Re: BUG #1947: Enhancement Request - CONCAT() function

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group