Re: Copy/Paste table(s) functions - git context patch

From: Vladimir Kokovic <vladimir(dot)kokovic(at)gmail(dot)com>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Copy/Paste table(s) functions - git context patch
Date: 2011-07-17 21:17:23
Message-ID: CAHsHPqcrmKZXb9Ln+8WeUUdp3b-woGMT+ku7=rA=ABgNRJJsrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

OK

> Now that we can copy on the same schema, it shouldn't ask for an
> extension, but for the complete name.

I do not know how to do when the table has objects that each has a name!

CREATE TABLE gk_vrsta_naloga_vk --NAME1
(
id bigint NOT NULL DEFAULT
nextval('"''id_gk_vrsta_naloga''"'::regclass), --NAME2
sifra character varying NOT NULL DEFAULT ''::character varying,
CONSTRAINT gk_vrsta_naloga_vk_pkey PRIMARY KEY (id), --NAME3
CONSTRAINT unique_gk_vrsta_naloga_vk1 UNIQUE (sifra, id), --NAME4
CONSTRAINT unique_gk_vrsta_naloga_vk2 UNIQUE (id, sifra), --NAME5
... --NAMEn
)
WITH (
OIDS=FALSE

Suffix is much better solution ...

On 7/17/11, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
> On Sun, 2011-07-17 at 21:44 +0200, Guillaume Lelarge wrote:
>> On Sun, 2011-07-17 at 20:41 +0200, Vladimir Kokovic wrote:
>> > I do not know what happened, but I am quite sure that it is not a
>> > frmPasteObject.cpp!
>> >
>>
>> OK, I did more testing, and the schema stuff is actually a bug I
>> introduced earlier. And while doing this, I found another one. Grest
>> evening :-/
>>
>
> s/Grest/Great/
>
> Both fixed.
>
> My other comments still apply.
>
>
> --
> Guillaume
> http://blog.guillaume.lelarge.info
> http://www.dalibo.com
>
>

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2011-07-18 08:23:23 Re: Website
Previous Message Guillaume Lelarge 2011-07-17 20:31:15 Re: Copy/Paste table(s) functions - git context patch