Re: Proposed Patchs

> -----Original Message-----
> From: Thomas Sondag [mailto:thomas(dot)sondag(at)gmail(dot)com]
> Sent: 29 May 2006 10:02
> To: Dave Page
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Proposed Patchs
>
> Hum, I miss this option ... sorry, but the main difference with the
> current behaviour is for object owning. The main idea was to set
> object owner to a group like that :
> database foo -> group foo
> schema bar -> group bar
> schema bar read user -> user toto
>
> I don't know if that's a good policy, but this case may exist, we may
> add an option like "Show Group for object owning" ?

Yes, that seems like a much better option - though I wonder if it should
default to just groups and then use the existing setting as per the
permissions. That would seem more consistent.

> The last bug I have is for database creation, I don't know how to get
> the current login.

Well dlgDatabase will automatically use the parent node's database (ie.
The maintenance DB) when appropriate so you should just be able to get
the username from that.

>From dlgDatabase.cpp

dlgProperty *pgDatabaseFactory::CreateDialog(frmMain *frame, pgObject
*node, pgObject *parent)
{
dlgDatabase *dlg=new dlgDatabase(this, frame, (pgDatabase*)node);
if (dlg && !node)
{
// use the server's connection to avoid "template1 in use"
dlg->connection=parent->GetConnection();
}
return dlg;
}

Regards, Dave.