Skip site navigation (1) Skip section navigation (2)

Re: Spurious errors relating to escaped single quotes

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Spurious errors relating to escaped single quotes
Date: 2011-07-17 02:53:01
Message-ID: 4E224E8D.7070803@archidevsys.co.nz (view raw or flat)
Thread:
Lists: pgsql-bugs
On 16/07/11 05:21, Tom Lane wrote:
> Gavin Flower<GavinFlower(at)archidevsys(dot)co(dot)nz>  writes:
>> On 15/07/11 11:25, Gavin Flower wrote:
>>> I think it should be possible to put a constraint on the master table
>>> to prevent rows being inserted.
>> Of course, minutes after I sent the above - I realized these constraints
>> are inherited, so the above is nonsense!  :-(
> Yeah.  I think there's been some discussion of inventing a non-inherited
> variety of check constraint, so that you could put something like
> "CHECK (false) NO INHERIT" on the parent table.  There's not really
> consensus for this though.
>
> IMO we'd be better advised to spend our time on building an explicit
> partitioning mechanism to handle the common cases more simply and
> efficiently, instead of continuing to add frammishes to the inheritance
> mechanism.
>
> 			regards, tom lane

How about being able to mark individual columns, and optionally the
table itself, as ABSTRACT?

Though, I agree that a proper partitioning mechanism would be better.

Cheers,
Gavin


In response to

pgsql-bugs by date

Next:From: Thomas PitschelDate: 2011-07-17 12:17:36
Subject: BUG #6121: error msg feature request for initial server tasks
Previous:From: Paula Andrea CarvajalDate: 2011-07-17 01:01:10
Subject: BUG #6120: Problem running post-install step in Mac OS X Lion (GM)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group