Re: More than one UNIQUE key when matching items..

2021-03-22 Thread Ron Clarke
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

Re: More than one UNIQUE key when matching items..

2021-03-22 Thread Ron Clarke
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 +0000, Ron Clarke wrote: > > In SQL Server this is easy, we insert the records into a tempor

More than one UNIQUE key when matching items..

2021-03-20 Thread Ron Clarke
/* 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

Re: Assigning values to a range in Pgsql and inclusive / exclusive bounds

2020-06-15 Thread Ron Clarke
Thanks for that perfect... missed the use of tstzrange() as a 'function' in the documentation. Best regards Ron On Fri, 12 Jun 2020 at 21:02, Adrian Klaver wrote: > On 6/12/20 11:45 AM, Ron Clarke wrote: > > Hi, > > > > I've got a simple problem, but I'm conv

Assigning values to a range in Pgsql and inclusive / exclusive bounds

2020-06-12 Thread Ron Clarke
Hi, I've got a simple problem, but I'm convinced that there must be an elegant solution. I'm a refugee from the world of MSSQL, so I'm still finding some aspects of PostgreSQL alien. I'm trying to use the *tstzrange *datatype. My issue is correctly setting the bound types when assigning values