Hi again,
one, possibly, last, thing. I wrote:
> I still find the CHECK constraint
> to be a more natural way to express what I want, though.
Now let me extend on this a bit.
The CHECK constraint says nicely and natively, what constraints (no
pun intended) I want the data to fulfil. With both t
Hi *,
I’ve tried both setting the constraints temporarily to invalid (works)
and converting (painstakingly slow, as this is new for me) to triggers
(also works). Both can be dumped and restored.
I’ve also found out that I probably can ship the schema update that
converts the CHECK constraint to a
On Fri, 31 Mar 2017, Adrian Klaver wrote:
> > ① that using a CHECK constraint to check data from another table
> > is wrong (but not why), and
>
> Because that is a documented limitation:
>
> https://www.postgresql.org/docs/9.6/static/sql-createtable.html
>
> "Currently, CHECK expressions can
Hi *,
while I’d still appreciate help on the bugreport (context is this…
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859033 … one), I’ve
found this… http://dba.stackexchange.com/a/75635/65843 … which says
① that using a CHECK constraint to check data from another table
is wrong (but not wh
