On 2018-Nov-20, Haribabu Kommi wrote:
> > > 4. Single API with -1 as invalid value, treat NULL as no matching. (Only
> > problem
> > > with this approach is till now -1 is also a valid queryid, but setting
> > -1 as queryid
> > > needs to be avoided.
> >
> > Hmm, can we use 0 as default value without any such caveat?
>
> Yes, with strict and 0 as default value can work.
> If there is no problem, I can go ahead with the above changes?
I'm not sure I understand this proposal. Does this mean that passing -1
as databaseid / userid would match all databases/users, and passing 0 as
queryid would match all queries? This would be suprising, since OID is
unsigned so -1 is a possibly valid value ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services