Re: Redundant statements - Mailing list pgadmin-hackers

From Guillaume Lelarge
Subject Re: Redundant statements
Date
Msg-id 4BDA0AFA.7040006@lelarge.info
Whole thread Raw
In response to Re: Redundant statements  (Erwin Brandstetter <brandstetter@falter.at>)
Responses Re: Redundant statements  (Erwin Brandstetter <brandstetter@falter.at>)
List pgadmin-hackers
Le 30/04/2010 00:35, Erwin Brandstetter a écrit :
> On 29.04.2010 18:48, guillaume@lelarge.info wrote:
>> Le 29/04/2010 17:50, Guillaume Lelarge a écrit :
>>
>>> Le 29/04/2010 17:28, Erwin Brandstetter a écrit :
>>>
>>>> On 29.04.2010 15:21, guillaume@lelarge.info wrote:
>>>>
>>> [...]
>>>
>>>>>> What do you think of it? Should I create a ticket?
>>>>>>
>>>>>>
>>>>> Well, I would like to have a better handling of the "SET STORAGE"
>>>>> statement. So, yes, you can create a ticket on that, without being too
>>>>> specific on the solution, which still needs some talk.
>>>>>
>>>>>
>>>> So we agree on "SET STORAGE". I'll create a ticket on that.
>>>>
>>>>
>>> Yeah. I also found how to detect the "initial" value of the storage
>>> (column typstorage in pg_catalog.pg_type). So I'll work on this right
>>> now.
>>>
>>>
>> Fixed. I can provide you a new pgAdmin3.exe quite easily if you want.
>>
>
> Cool. If you provide me with a new pgAdmin3.exe I will use it for tests.

On it.

> We are moving in on a point release v1.10.3, aren't we? I found 21
> resolved bugs tagged "1.10.3" in trac - compared to 9 for v1.10.2. So we
> might call it early alpha-testing?
>

Not right now. Dave is working on getting out beta 1 for pgAdmin 1.12. I
don't think he has the time to prepare a new 1.10 minor release, and I'm
not sure this is the perfect timing for it. But I hope we'll have one
before 1.12 is final.


--
Guillaume.
 http://www.postgresqlfr.org
 http://dalibo.com

pgadmin-hackers by date:

Previous
From: "pgAdmin Trac"
Date:
Subject: Re: [pgAdmin III] #14: Save graphical explain output
Next
From: Erwin Brandstetter
Date:
Subject: Re: Redundant statements