Re: [INTERFACES] Re: [HACKERS] changes in 6.4

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