Thread: BUG with decimal type

Hi,

sorry if this is already fixed, but under Postgres 6.5.1. (debian 6.5.1-6)
the following ..

create table VAT (  objectid     integer not null primary key,  ts           integer not null,  vatlevel
decimal(18,2)not null,  orderby      integer not null
 
);
create unique index VAT_level_idx on VAT ( vatlevel );

.. yields:

"ERROR:  Can't find a default operator class for type 1700."

Regards,

-- 
Jens Glaser     Am Holderstrauch 13, 36041 Fulda, 0661/9429507    jens@jens.de

>
> Hi,
>
> sorry if this is already fixed, but under Postgres 6.5.1. (debian 6.5.1-6)
> the following ..
>
> create table VAT (
>    objectid     integer not null primary key,
>    ts           integer not null,
>    vatlevel     decimal(18,2) not null,
>    orderby      integer not null
> );
> create unique index VAT_level_idx on VAT ( vatlevel );
>
> .. yields:
>
> "ERROR:  Can't find a default operator class for type 1700."


    Not fixed - but well known.


Jan

PS:  I'm  not  dead.  The  problem  is  that  there  are not only
    priorities on my TODO's. They are organized in separate lists
    where each list has a master-priority.

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

Jens Glaser <jens@helena.jens.de> writes:
> "ERROR:  Can't find a default operator class for type 1700."

Yeah, there's no support yet for indexes on NUMERIC (DECIMAL) fields :-(.
It's on the TODO list...
        regards, tom lane