Great, thanks!
Best,
Manuel
On Thu, May 2, 2019 at 6:25 PM Richard Hipp wrote:
> Documentation has been updated in an attempt to clarify when UPSERT
> applies and when it does not.
>
> On 5/2/19, Manuel Rigger wrote:
> > Okay, thanks for the clarification!
> >
> > I think that this part of the
Documentation has been updated in an attempt to clarify when UPSERT
applies and when it does not.
On 5/2/19, Manuel Rigger wrote:
> Okay, thanks for the clarification!
>
> I think that this part of the documentation is ambiguous. The part of the
> documentation that you quoted mentions a "conflic
Okay, thanks for the clarification!
I think that this part of the documentation is ambiguous. The part of the
documentation that you quoted mentions a "conflict target", but there is no
conflict target in the example that I provided. The documentation
continues by stating that a conflict target i
On 5/2/19, Manuel Rigger wrote:
> Hi everyone,
>
> It seems that upsert does not take into account "NOT NULL" constraints. In
> the example below, I get an error "NOT NULL constraint failed: test.c0":
>
> CREATE TABLE test (c0 NOT NULL);
> INSERT INTO test(c0) VALUES (NULL) ON CONFLICT DO NOTHING;
Hi everyone,
It seems that upsert does not take into account "NOT NULL" constraints. In
the example below, I get an error "NOT NULL constraint failed: test.c0":
CREATE TABLE test (c0 NOT NULL);
INSERT INTO test(c0) VALUES (NULL) ON CONFLICT DO NOTHING;
I would have expected that the second state
5 matches
Mail list logo