>
Is this more involved than creating a list of all valid Unicode characters
(~144 thousand), sorting them, then running crc32 over the sorted order to
create the "version" for the library/collation pair? Far from free but few
databases use more than a couple different collations.
--
Rod Taylor
ferent symbol which expands to a more
selective column set. Perhaps by default it picks up short textish columns;
skip bytea or long text fields for example but can be adjusted with HIDDEN.
Perhaps "SELECT +"?
--
Rod Taylor
d record.
ALTER TABLE order ADD customer record GENERATED JOIN customer USING
(customer_id) VIRTUAL;
ALTER TABLE order_detail ADD order record GENERATED JOIN order USING
(order_id) VIRTUAL;
SELECT order.customer.company_name FROM order_detail;
Of course, if they don't reference the GENERATED column then the join isn't
added to the query.
--
Rod Taylor
On Sat, 17 Nov 2018 at 14:32, Tom Lane wrote:
> Rod Taylor writes:
> > Should now/current_date be marked leakproof?
>
> Since it has no argument, that should be moot.
>
Gah, you're right.
It seems to be because the below clause is timestamp without time zone:
WHERE cur
Should now/current_date be marked leakproof?
I'm trying to push a `WHERE field >= current_date - interval '1 day'` type
of clause into a security_barrier defined view.
--
Rod Taylor
