Hey thanks for working out a solution to this deceptive problem. One of
those you expect to be simple, but then all of a sudden it isn't.
Best regards
Ron
On Sat, 20 Mar 2021 at 19:01, Allan Kamau wrote:
>
>
>
>
>
>
> On Sat, Mar 20, 2021 at 6:52 PM Ron Clarke wrote:
>
>> /*
>> I'm tryin
Thank you, simple, and effective. Got sucked into trying to use a named
constraint.
Best regards
Ron
On Sat, 20 Mar 2021 at 20:00, Laurenz Albe wrote:
> On Sat, 2021-03-20 at 15:51 +, Ron Clarke wrote:
> > In SQL Server this is easy, we insert the records into a temporary table
> with separ
On Sat, 2021-03-20 at 15:51 +, Ron Clarke wrote:
> In SQL Server this is easy, we insert the records into a temporary table with
> separate Unique
> indexes on the id for set a and the ids for set b and put the
> 'ignore_dup_key' on which tells
> SQL Server to ignore duplicate rows and carr
On Sat, Mar 20, 2021 at 6:52 PM Ron Clarke wrote:
> /*
> I'm trying to port a system from SQL server, and at the same time better
> learn postgreSQL.
>
> I've come across a problem that is easily solved in that world, but I am
> struggling to find an approach in postgres that works.
>
> We have 2
/*
I'm trying to port a system from SQL server, and at the same time better
learn postgreSQL.
I've come across a problem that is easily solved in that world, but I am
struggling to find an approach in postgres that works.
We have 2 sets of events A and B (sets), they have a shared number (ncode),
