On Wed, Dec 19, 2007 at 10:41:36PM +0100, GMail wrote:
> By the way, why not allowing the declaration of an index over a composite
> type as a whole? (As opposed to a composite type as the list of single
> component types).
It would probably work if there was an operator class defined for your
typ
Il Wednesday 19 December 2007 22:29:25 Colin Wetherbee ha scritto:
> GMail wrote:
> > When trying to create an index on a composite type, I need to enclose
> > the columns in paranthesis. Is this normal?
> > I don't think so as there's no mention in the friendly manual.
>
> I think your problem is
GMail wrote:
When trying to create an index on a composite type, I need to enclose
the columns in paranthesis. Is this normal?
I don't think so as there's no mention in the friendly manual.
I think your problem is similar to one that has been discussed here
previously.
http://www.mail-archiv
On Wed, Dec 19, 2007 at 10:07:32PM +0100, GMail wrote:
> Hi all.
>
> When trying to create an index on a composite type, I need to enclose
> the columns in paranthesis. Is this normal?
> I don't think so as there's no mention in the friendly manual.
I beleive it says somewhere that anything excep
Hi all.
When trying to create an index on a composite type, I need to enclose
the columns in paranthesis. Is this normal?
I don't think so as there's no mention in the friendly manual.
An example:
create type atype as (
atext text,
anint int
);
create table atable (
info text,
compo aty
