| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Blake McBride <blake(at)mcbride(dot)name> |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: Cut / Paste issue |
| Date: | 2011-06-13 22:29:28 |
| Message-ID: | 1308004169.1969.20.camel@laptop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
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.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2011-06-13 22:32:33 | Re: Cut / paste part 2 |
| Previous Message | Blake McBride | 2011-06-13 20:49:00 | Cut / paste part 2 |