Re: Schema and tablespace

> ------- Original Message -------
> From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
> To: Magnus Hagander <magnus(at)hagander(dot)net>
> Sent: 17/12/07, 22:23:50
> Subject: Re: [pgadmin-hackers] Schema and tablespace
>
> I've thought about this too but I didn't find a place where I can put
> this new listview : another tab near the properties one ? this does not
> feel consistent to me. That's why I still prefer to continue the
> treeview... but if you have a better idea, I'm eager to know it :)

Don't we get this for free from the dependents tab?

For the record, I don't want to list objects under tablespaces on the treeview - that would cause even more dependency/refresh issues than we have now.

/D

Dave Page wrote:
>
>> ------- Original Message -------
>> From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
>> To: Magnus Hagander <magnus(at)hagander(dot)net>
>> Sent: 17/12/07, 22:23:50
>> Subject: Re: [pgadmin-hackers] Schema and tablespace
>>
>> I've thought about this too but I didn't find a place where I can put
>> this new listview : another tab near the properties one ? this does not
>> feel consistent to me. That's why I still prefer to continue the
>> treeview... but if you have a better idea, I'm eager to know it :)
>
> Don't we get this for free from the dependents tab?
>
> For the record, I don't want to list objects under tablespaces on the treeview - that would cause even more dependency/refresh issues than we have now.
>

That was one of the issue I had : refresh is a bit of a nightmare. I
think I'll try the listview in a new tab. But first, I'll get a look at
the dependents tab but I'm not sure I will find a size column in there.

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

Guillaume Lelarge wrote:
> Dave Page wrote:
>>> ------- Original Message -------
>>> From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
>>> To: Magnus Hagander <magnus(at)hagander(dot)net>
>>> Sent: 17/12/07, 22:23:50
>>> Subject: Re: [pgadmin-hackers] Schema and tablespace
>>>
>>> I've thought about this too but I didn't find a place where I can put
>>> this new listview : another tab near the properties one ? this does not
>>> feel consistent to me. That's why I still prefer to continue the
>>> treeview... but if you have a better idea, I'm eager to know it :)
>> Don't we get this for free from the dependents tab?
>>
>> For the record, I don't want to list objects under tablespaces on the treeview - that would cause even more dependency/refresh issues than we have now.
>>
>
> That was one of the issue I had : refresh is a bit of a nightmare. I
> think I'll try the listview in a new tab. But first, I'll get a look at
> the dependents tab but I'm not sure I will find a size column in there.
>
>

I'm not entirely sure we're on the same page. All we need to do it see
what's in a tablespace right? We should see that already because the
Dependents tab will list all object that are dependent upon the
tablespace in some way. We get the size and other details from the node
in the treeview for each object - that's all data that I don't want to
duplicate.

/D

Dave Page wrote:
> Guillaume Lelarge wrote:
>>>[...]
>> That was one of the issue I had : refresh is a bit of a nightmare. I
>> think I'll try the listview in a new tab. But first, I'll get a look at
>> the dependents tab but I'm not sure I will find a size column in there.
>>
>
> I'm not entirely sure we're on the same page. All we need to do it see
> what's in a tablespace right?

Not really. As Magnus said, we need to see what's in the tablespace and
the size of each object.

> We should see that already because the
> Dependents tab will list all object that are dependent upon the
> tablespace in some way. We get the size and other details from the node
> in the treeview for each object - that's all data that I don't want to
> duplicate.

I'm not interested in "the other details" but I think a list of objects
with their size is important. Usually, one use a tablespace when one
needs more disk space. With this, you can see quickly the disk space
used in the tablespace.

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

Guillaume Lelarge wrote:
> Dave Page wrote:
>> Guillaume Lelarge wrote:
>>>> [...]
>>> That was one of the issue I had : refresh is a bit of a nightmare. I
>>> think I'll try the listview in a new tab. But first, I'll get a look at
>>> the dependents tab but I'm not sure I will find a size column in there.
>>>
>> I'm not entirely sure we're on the same page. All we need to do it see
>> what's in a tablespace right?
>
> Not really. As Magnus said, we need to see what's in the tablespace and
> the size of each object.

Hmm - I'm not too keen on the idea of adding a special tab for this one
purpose. How about handling this in a similar way to how we display the
EDB system catalogs, in which we have a special pseudo-object called a
'catalog object' which gives a generic representation of a view or
table? We would have a collection of 'tablespace objects' under the
tablespace, with limited properties of name, schema, oid, size, comment
and anything else thats suitably generic that I've forgotten.

That would also allow the reporting engine to be used easily...

/D

Dave Page wrote:
> Guillaume Lelarge wrote:
>> Dave Page wrote:
>>> Guillaume Lelarge wrote:
>>>>> [...]
>>>> That was one of the issue I had : refresh is a bit of a nightmare. I
>>>> think I'll try the listview in a new tab. But first, I'll get a look at
>>>> the dependents tab but I'm not sure I will find a size column in there.
>>>>
>>> I'm not entirely sure we're on the same page. All we need to do it see
>>> what's in a tablespace right?
>> Not really. As Magnus said, we need to see what's in the tablespace and
>> the size of each object.
>
> Hmm - I'm not too keen on the idea of adding a special tab for this one
> purpose. How about handling this in a similar way to how we display the
> EDB system catalogs, in which we have a special pseudo-object called a
> 'catalog object' which gives a generic representation of a view or
> table? We would have a collection of 'tablespace objects' under the
> tablespace, with limited properties of name, schema, oid, size, comment
> and anything else thats suitably generic that I've forgotten.
>

Seems to be good for me. I'll try to find some time to look at this.

> That would also allow the reporting engine to be used easily...
>

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