Re: Replace l337sp34k in comments.

From: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
To: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
Cc: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Replace l337sp34k in comments.
Date: 2021-07-30 08:05:53
Message-ID: CAEzk6feHr79DNa==-7zo3JahkFhGC_hAi8Z9TaMPMfjaO+PbLg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 29 Jul 2021 at 22:46, Gavin Flower
<GavinFlower(at)archidevsys(dot)co(dot)nz> wrote:
> Though in code, possibly it would be better to just use 'up-to-date' in
> code for consistency and to make the it easier to grep?

If it's causing an issue, perhaps using a less syntactically
problematic synonym like "current" might be better?

:)

Geoff

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Pyhalov 2021-07-30 08:16:53 Re: Case expression pushdown
Previous Message Dean Rasheed 2021-07-30 07:26:14 Division by zero error in to_char(num, '9.9EEEE')