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

Re: No default operator type for indexes for numeric fields???

From: Mike Mascari <mascarm(at)mascari(dot)com>
To: Constantin Teodorescu <teo(at)flex(dot)ro>
Cc: PostgreSQL Interfaces <pgsql-interfaces(at)postgresql(dot)org>
Subject: Re: No default operator type for indexes for numeric fields???
Date: 2000-04-11 14:07:55
Message-ID: 38F331BB.638CA329@mascari.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
Constantin Teodorescu wrote:
> 
> I have the following table structure:
> 
> +----------+-----------------------------+-------+
> |  Field   |              Type           | Length|
> +----------+-----------------------------+-------+
> | perioada | int2 not null               |     2 |
> | gestiune | int2 not null               |     2 |
> | produs   | int4 not null               |     4 |
> | pret     | numeric not null            | 30.2  |
> | initial  | numeric not null default 0  | 25.3  |
> | intrari  | numeric not null default 0  | 25.3  |
> | iesiri   | numeric not null default 0  | 25.3  |
> +----------+-----------------------------+-------+
> 
> Trying to create an index like
> 
> create unique index stocuri_pkey on stocuri
> (perioada,gestiune,produs,pret);
> 
> I got the following error:
> 
> ERROR:  Can't find a default operator class for type 1700.
> 
> How should I create an index using a numeric field?
> 
> Constantin Teodorescu
> FLEX Consulting Braila, ROMANIA

According to the release history, this appears to be something
that has been added for 7.0:

Types
-----
...
Add btree index on NUMERIC(Jan)
...


Mike Mascari

In response to

pgsql-interfaces by date

Next:From: Paolo SommarugaDate: 2000-04-11 14:23:56
Subject: Re: Why fields order is wrong ?
Previous:From: Constantin TeodorescuDate: 2000-04-11 13:36:51
Subject: No default operator type for indexes for numeric fields???

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