Re: [pgadmin-hackers] New macros for sequence node [pgadmin4]

2016-03-03 Thread Dave Page
Thanks - patch applied. On Wed, Feb 10, 2016 at 2:00 PM, Harshal Dhumal < harshal.dhu...@enterprisedb.com> wrote: > + Usage of macros > > > Way to use in template: > > *1] Security labels:* > > SECLABLE.SET(conn, object_type, object_name, provider, security_label, > object.schema) > >

Re: [pgadmin-hackers] New macros for sequence node [pgadmin4]

2016-02-10 Thread Harshal Dhumal
Hi, PFA patch for schema macros for security and privilege. Now I have moved macros related to schema and its child object under schemas/templates/macros/schemas folder -- *Harshal Dhumal* *Software Engineer * EenterpriseDB On Wed, Feb 10, 2016 at 5:41 PM,

Re: [pgadmin-hackers] New macros for sequence node [pgadmin4]

2016-02-10 Thread Harshal Dhumal
+ Usage of macros Way to use in template: *1] Security labels:* SECLABLE.SET(conn, object_type, object_name, provider, security_label, object.schema) SECLABLE.UNSET(conn, object_type, object_name, provider, object.schema) *2] Privileges:* PRIVILEGE.SET(conn, object_type, grantee,

Re: [pgadmin-hackers] New macros for sequence node [pgadmin4]

2016-02-10 Thread Harshal Dhumal
Hi, Here is updated patch for macros. I have added required validation in macros. -- *Harshal Dhumal* *Software Engineer * EenterpriseDB On Wed, Feb 10, 2016 at 1:06 PM, Ashesh Vashi wrote: > On Tue, Feb 9, 2016 at 3:48 PM,

[pgadmin-hackers] New macros for sequence node [pgadmin4]

2016-02-09 Thread Harshal Dhumal
Hi, PFA of macros (privilege, security) for sequence node. Also fixed minor issue in security macro (removed unwanted qtIdent for provider) -- *Harshal Dhumal* *Software Engineer * EenterpriseDB diff --git

Re: [pgadmin-hackers] New macros for sequence node [pgadmin4]

2016-02-09 Thread Ashesh Vashi
On Tue, Feb 9, 2016 at 3:48 PM, Harshal Dhumal < harshal.dhu...@enterprisedb.com> wrote: > Hi, > > PFA of macros (privilege, security) for sequence node. > > Also fixed minor issue in security macro (removed unwanted qtIdent for > provider) > This is not allowed. We can't pass on the data coming