From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgAdmin III commit: Add support for range types (9.2+) |
Date: | 2012-04-30 15:02:51 |
Message-ID: | CAA-aLv4QCJTDf9NgDHabZJ_+9Y6iCW26rm3o861vnOrzCpTRbg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On 30 April 2012 15:57, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
> On Mon, 2012-04-30 at 15:47 +0100, Thom Brown wrote:
>> On 30 April 2012 15:44, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
>> > On Sun, 2012-04-29 at 22:22 +0100, Thom Brown wrote:
>> >> On 29 April 2012 21:56, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
>> >> > Add support for range types (9.2+)
>> >>
>> >> Range types aren't added to the type drop-down and instead only show
>> >> the array-equivalents.
>> >>
>> >
>> > You mean on the function properties dialog, right?
>>
>> No, I mean when you go to create a table, then add a column, the
>> constituent range types aren't listed, only their array equivalents.
>> For example, I can't create a table in the GUI which contains a column
>> using the int4range type, but I can use the int4range[] type instead.
>
> OK, should be fixed now.
>
> Thanks Thom.
Yes, looks fine now. Thanks.
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2012-05-01 09:03:45 | pgAdmin III commit: Lots of work on domains, and check constraints |
Previous Message | Guillaume Lelarge | 2012-04-30 14:57:56 | Re: pgAdmin III commit: Add support for range types (9.2+) |