Обсуждение: TODO item: columns of Views: show properties
I see in todo an item:
columns of Views: show properties
and maybe I have a solution. I have written a "c" (backend) function that
can return the same structure as "pg_class" for any query, and that means
indirectly that it can return all columns definitions for view too. It is
important that it can tell for each column to which table it belongs.
Concerning pgAdmin already has some server-side functions, could this be a
solution ?
Regards !
Darko Prenosil wrote: > I see in todo an item: > columns of Views: show properties > > and maybe I have a solution. I have written a "c" (backend) function that > can return the same structure as "pg_class" for any query, and that means > indirectly that it can return all columns definitions for view too. It is > important that it can tell for each column to which table it belongs. > Concerning pgAdmin already has some server-side functions, could this be a > solution ? No, server-side support functions are really only the very last solution to consider. pgAdmin3 should run out-of-the-box as much as possible. What has to be done is put all applicable table subitems under view also. Regards, Andreas
On Tuesday 17 August 2004 03:02, Andreas Pflug wrote: > Darko Prenosil wrote: > > I see in todo an item: > > columns of Views: show properties > > > > and maybe I have a solution. I have written a "c" (backend) function that > > can return the same structure as "pg_class" for any query, and that means > > indirectly that it can return all columns definitions for view too. It is > > important that it can tell for each column to which table it belongs. > > Concerning pgAdmin already has some server-side functions, could this be > > a solution ? > > No, server-side support functions are really only the very last solution > to consider. pgAdmin3 should run out-of-the-box as much as possible. > What has to be done is put all applicable table subitems under view also. > > In that case I have no idea how to do it :-( In server-side function I can use parser interface to obtain all column definitions, have no idea how to do it on the client side. Regards !
Darko Prenosil wrote: > > In that case I have no idea how to do it :-( Just as for tables. If you're looking for some TODO item to complete, you could check if all properties react properly (i.e. are read only, and menu items are disabled) if a user has no superuser privilege. Knowing which objects fail would help fixing it. Regards, Andreas
OK, I'll take a look. Regards ! On Tuesday 17 August 2004 13:28, Andreas Pflug wrote: > Darko Prenosil wrote: > > In that case I have no idea how to do it :-( > > Just as for tables. > > If you're looking for some TODO item to complete, you could check if all > properties react properly (i.e. are read only, and menu items are > disabled) if a user has no superuser privilege. Knowing which objects > fail would help fixing it. > > Regards, > Andreas > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
Calling property dialog on database for non-superuser crashes the application. Anyone else seeing this ? I'm trying to figure out what is happening. Regards ! On Tuesday 17 August 2004 12:35, Darko Prenosil wrote: > OK, I'll take a look. > Regards ! > > On Tuesday 17 August 2004 13:28, Andreas Pflug wrote: > > Darko Prenosil wrote: > > > In that case I have no idea how to do it :-( > > > > Just as for tables. > > > > If you're looking for some TODO item to complete, you could check if all > > properties react properly (i.e. are read only, and menu items are > > disabled) if a user has no superuser privilege. Knowing which objects > > fail would help fixing it. > > > > Regards, > > Andreas > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)