pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vadim Mikheev <vadim@krs.ru>
To: Hannu Krosing <hannu@trust.ee>
Cc: Bruce Momjian <maillist@candle.pha.pa.us>
Cc: pgsql-interfaces@postgreSQL.org
Cc: hackers@postgreSQL.org
Subject: Re: [INTERFACES] Re: [HACKERS] changes in 6.4
Date: Thu, 16 Jul 1998 04:25:44 +0800
Message-ID: <35AD1048.97441728@krs.ru> (raw)
References: <199807141537.LAA24391@candle.pha.pa.us>
	<35AD0879.2EA15E8B@trust.ee>

Hannu Krosing wrote:
> 
> Not requiring the column to sort on in target list ia also quite
> important.

I'm not sure but isn't this already in 6.4-current ?

> 
> As are the (still elementary) constraints, still elementary becuse
> there is no way to use functions or "is null" in check constraint,

ispas=> create table t (x int, check (x is null or x = 5));
CREATE
ispas=> insert into t values (1);
ERROR:  ExecAppend: rejected due to CHECK constraint $1
ispas=> insert into t values (null);
INSERT 168212 1
ispas=> insert into t values (5);
INSERT 168213 1

And I'm sure that functions are supported too. This is 6.3.2

> and constraints can be used only when defining tables, not in
> "alter table" construct.

I hadn't time to do this when implementing and have no plans
to do this. In "near" future :)

> 
> > The days where every release fixed server crashes, or added a feature
> > that users were 'screaming for' may be a thing of the past.
> 
> Is anyone working on fixing the exploding optimisations for many OR-s,
> at least the canonic case used by access?
> 
> My impression is that this has fallen somewhere between
> insightdist and Vadim.

I'm not working...

Vadim



view thread (29+ messages)  latest in thread

Message-ID: <35AD1048.97441728@krs.ru>
Permalink:  ../35AD1048.97441728@krs.ru/
Also on:    postgresql.org/message-id/35AD1048.97441728@krs.ru

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: vadim@krs.ru, hannu@trust.ee, maillist@candle.pha.pa.us, hackers@postgreSQL.org
  Subject: Re: [INTERFACES] Re: [HACKERS] changes in 6.4
  In-Reply-To: <35AD1048.97441728@krs.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox