Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by postgresql.org (8.11.3/8.11.1) with SMTP id f5C2REE89636 for ; Mon, 11 Jun 2001 22:27:14 -0400 (EDT) (envelope-from Inoue@tpf.co.jp) Received: (qmail 18468 invoked from network); 12 Jun 2001 02:27:08 -0000 Received: from unknown (HELO viscomail.tpf.co.jp) (100.0.0.108) by sd2.10.0.100.in-addr.arpa with SMTP; 12 Jun 2001 02:27:08 -0000 Received: from tpf.co.jp ([126.0.1.68]) by viscomail.tpf.co.jp (8.8.8+Sun/8.8.8) with ESMTP id LAA23235; Tue, 12 Jun 2001 11:27:01 +0900 (JST) Message-ID: <3B257E30.8171C119@tpf.co.jp> Date: Tue, 12 Jun 2001 11:28:00 +0900 From: Hiroshi Inoue X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: Simon Emmanuel Rivas CC: pgsql-interfaces@postgresql.org Subject: Re: ODBC problem References: <3B1F3638.79D8E4B8@isr.thomson-csf.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Archive-Number: 200106/49 X-Sequence-Number: 1712 Simon Emmanuel Rivas wrote: > > Hi! > > I have a problem using the ODBC interface. The problem is quite simple: > I have created a table with only one field, as follows: > create table test (key numeric(1)); > Very simple, right? The problem is that, when I look at this table > through a client program which runs under Windows (postgres runs under > Linux), the field "key" seems to be declared as numeric(3). > Does the problem come from ODBC or the client program? The problem seems to come from the client program. For example, M$ Access recognizes numeric(1). regards, Hiroshi Inoue