On 19/11/2018 06:18, Haribabu Kommi wrote: > Amit suggested another option in another mail, so total viable > solutions that are discussed as of now are, > > 1. Single API with NULL input treat as invalid value > 2. Multiple API to deal with NULL input of other values > 3. Single API with NULL value to treat them as current user, current > database > and NULL queryid. > 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.
Can you show examples of what these would look like? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
