Thread: Cut / Paste issue
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. Thanks. Blake McBride
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
On Tue, 2011-06-14 at 00:29 +0200, Guillaume Lelarge 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. > And you can change it in the options dialog (tab "Query tool", checkbox "Result copy quote character"). -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com
On Monday, June 13, 2011, Guillaume Lelarge <guillaume@lelarge.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