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

Re: Cut / Paste issue

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: Blake McBride <blake(at)mcbride(dot)name>, "pgadmin-hackers(at)postgresql(dot)org" <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Cut / Paste issue
Date: 2011-06-13 22:52:06
Message-ID: BANLkTikcivnF=Zivhe0H=pKkj8nH+q0fxA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgadmin-hackers
On Monday, June 13, 2011, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
> On Mon, 2011-06-13 at 15:39 -0500, Blake McBride wrote:
>> Greetings,
>>
>> Interesting inconsistency in the cut / paste operation in pgAdmin.  I
>> am using 1.14.0 beta 2.
>>
>> If you View the top 100 rows you get a spreadsheet like display
>> showing the rows.  If you then select a row (not its data) and copy
>> it.  You then paste it (to the scratch pad buffer below for example)
>> and the paste operation puts double quotes around the data.  This is a
>> real pain because SQL uses single quotes.  If you attempt to use the
>> data in a query you have to replace the double quotes auto-added in
>> the paste operation with single quotes.  It would be better if it
>> auto-added single quotes.  This would be more consistent with SQL.
>>
>
> But the copy doesn't try to be compatible with SQL. It's a CSV-like
> copy.
>

Right - the defaults should work nicely for pasting into apps like Excel.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgadmin-hackers by date

Next:From: Luis OchoaDate: 2011-06-14 04:31:00
Subject: Looking for suggestions about how should I implement an action at database designer UI
Previous:From: Guillaume LelargeDate: 2011-06-13 22:33:11
Subject: Re: Cut / Paste issue

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