On 6/4/21 11:21 AM, Adrian Klaver wrote:
On 6/4/21 10:37 AM, Laura Smith wrote:
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, 4 June 2021 18:11, Julien Rouhaud wrote:
On Sat, Jun 5, 2021 at 12:48 AM Laura Smith
n5d9xq3ti233xiyif...@protonmail.ch wrote:
A
> On Jun 4, 2021, at 11:55 AM, Laura Smith
> wrote:
>
> That seems to have done the trick. Thanks again Mark
Glad to hear it. Good luck.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, 4 June 2021 18:45, Mark Dilger wrote:
> > On Jun 4, 2021, at 9:47 AM, Laura Smith n5d9xq3ti233xiyif...@protonmail.ch
> > wrote:
> > CREATE TABLE test (
> > t_val text not null,
> > t_version text unique not null
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, 4 June 2021 18:45, Mark Dilger wrote:
> > On Jun 4, 2021, at 9:47 AM, Laura Smith n5d9xq3ti233xiyif...@protonmail.ch
> > wrote:
> > CREATE TABLE test (
> > t_val text not null,
> > t_version text unique not null
On 6/4/21 1:32 PM, Laura Smith wrote:
What is the solution then ? I need to keep historical versions but
at the same time I need a "current" version. If I am not able to use
"infinity" as bounds for "current" version then clearly I'm wasting
my time trying to use EXCLUDE AS for version tracking
On 6/4/21 10:37 AM, Laura Smith wrote:
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, 4 June 2021 18:11, Julien Rouhaud wrote:
On Sat, Jun 5, 2021 at 12:48 AM Laura Smith
n5d9xq3ti233xiyif...@protonmail.ch wrote:
All the examples I've seen around the inter
On 6/4/21 10:37 AM, Laura Smith wrote:
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, 4 June 2021 18:11, Julien Rouhaud wrote:
On Sat, Jun 5, 2021 at 12:48 AM Laura Smith
n5d9xq3ti233xiyif...@protonmail.ch wrote:
All the examples I've seen around the inter
> On Jun 4, 2021, at 9:47 AM, Laura Smith
> wrote:
>
> CREATE TABLE test (
> t_val text not null,
> t_version text unique not null default gen_random_uuid() ,
> t_range tstzrange not null default tstzrange('-infinity','infinity'),
> EXCLUDE USING gist (t_val WITH=, t_range WITH &&) DEFERRABLE
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, 4 June 2021 18:11, Julien Rouhaud wrote:
> On Sat, Jun 5, 2021 at 12:48 AM Laura Smith
> n5d9xq3ti233xiyif...@protonmail.ch wrote:
>
> > All the examples I've seen around the internet make this sound so easy.
> >
‐‐‐ Original Message ‐‐‐
On Friday, 4 June 2021 18:07, Adrian Klaver wrote:
> On 6/4/21 9:47 AM, Laura Smith wrote:
>
> > All the examples I've seen around the internet make this sound so easy.
> > But I seem to be missing some important step because all I'm getting are
> > messages su
On Sat, Jun 5, 2021 at 12:48 AM Laura Smith
wrote:
>
> All the examples I've seen around the internet make this sound so easy.
>
> But I seem to be missing some important step because all I'm getting are
> messages such as "DETAIL: Key (t_val, t_version)=(def, [-infinity,infinity))
> conflicts
On 6/4/21 9:47 AM, Laura Smith wrote:
All the examples I've seen around the internet make this sound so easy.
But I seem to be missing some important step because all I'm getting are messages such as
"DETAIL: Key (t_val, t_version)=(def, [-infinity,infinity)) conflicts with existing key
(t_va
All the examples I've seen around the internet make this sound so easy.
But I seem to be missing some important step because all I'm getting are
messages such as "DETAIL: Key (t_val, t_version)=(def, [-infinity,infinity))
conflicts with existing key (t_val, t_version)=(def, [-infinity,"2021-06-
13 matches
Mail list logo