pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Constantin Teodorescu <teo@flex.ro>
To: Jose' Soares Da Silva <sferac@bo.nettuno.it>
To: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>
Cc: PostgreSQL Questions <pgsql-questions@postgresql.org>
Subject: Re: [INTERFACES] pgaccess 0.86 - wrong field sizes
Date: Mon, 25 May 1998 15:17:53 +0300
Message-ID: <35696171.2A8019FF@flex.ro> (raw)
References: <Pine.LNX.3.96.980525124609.994A-100000@proxy.bazzanese.com>

Jose' Soares Da Silva wrote:
> 
> pgaccess displays the wrong size for types varchar (see your phonebook
> example):
> 
> table name      phonebook
> owner           marco
> field information:
> ---------------------------------------
> field name      field type      size
> ---------------------------------------
> name            varchar         -5           <-- (32)


Yes. I know!

There were some changes in system tables struct between 6.2.1 and 6.3
and PgAccess is reporting wrong the varchar field size.

Is there anyone who could send me the appropriate SQL  query that must
be used in order to determine the field name, types and sizes in 6.3.2
version?

I didn't found any time to hack a bit the new system table structures.

-- 
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA



Message-ID: <35696171.2A8019FF@flex.ro>
Permalink:  ../35696171.2A8019FF@flex.ro/
Also on:    postgresql.org/message-id/35696171.2A8019FF@flex.ro

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: teo@flex.ro, sferac@bo.nettuno.it, pgsql-questions@postgresql.org
  Subject: Re: [INTERFACES] pgaccess 0.86 - wrong field sizes
  In-Reply-To: <35696171.2A8019FF@flex.ro>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox