On Wed, Oct 10, 2018 at 10:14:23PM +0900, fn ln wrote:
> Hello.
>
> I've found this on the docs:
> https://www.postgresql.org/docs/devel/static/plpgsql-control-structures.html#
> PLPGSQL-STATEMENTS-RETURNING-PROCEDURE
> > If a RETURN statement is desired to exit the code early, then NULL must be
>
On Sat, Oct 6, 2018 at 08:17:04AM +0900, Tatsuo Ishii wrote:
> In "18.9.3. Creating Certificates",
>
> --
> To create a server certificate whose identity can be validated by
> clients, first create a certificate signing request (CSR)
On Sat, Oct 13, 2018 at 12:25:38PM +0300, KES wrote:
> >or NULL if any of the comparisons result in unknown
> result in unknown??
Well, SQL has a three-valued logic, and UNKOWN values are treated like
NULL. For me they have always been the same, and I would like to avoid
"unknown" in this context
>or NULL if any of the comparisons result in unknownresult in unknown?? 13.10.2018, 00:37, "David G. Johnston" :On Fri, Oct 12, 2018 at 8:04 AM Bruce Momjian wrote:Sorry, but I don't like this wording. The problem is that the
comparison has two row sets --- the left-hand side, a