pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurent Duperval <lduperval@microcelli5.com>
To: peter_e@gmx.net
Cc: pgsql-sql@postgresql.org
Subject: Re: varbit question
Date: Tue, 15 May 2001 11:47:59 -0400 (EDT)
Message-ID: <20010515154832.67F7846891@lenard.microcelli5.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0105151740520.757-100000@peter.localdomain>

On 15 May, Peter Eisentraut wrote:
> Laurent Duperval writes:
> 
>> I have an Oracle script that I want to convert to pgsql. I've got a sed
>> script that does most of the mappings but it doesn't look like raw is
>> supported. In the docs, there is mention of varbit(n) but if I use the
>> (n) argument, the script fails. I can only use varbit alone. How do I get
>> around that?
> 
> If you're not using version 7.1 or later you might want to upgrade.  The
> bit string types do not work correctly in earlier releases.  If you are
> using that version, please post more detail.
> 

Turns out it's a bug in the docs, I think. The table of all data types
mentions the following:

Type Name        Aliases        Description
bit                             fixed-length bit string
bit varying(n)   varbit(n)      variable-length bit string

but if you read a bit further in the Bit string types section, it
says:

  There are two SQL bit types: BIT(x) and BIT VARYING(x); the x specifies the
  maximum length.  BIT type data is automatically padded with 0's on the right
  to the maximum length, BIT VARYING is of variable length.   BIT without
  length is equivalent to BIT(1), BIT VARYING means unlimited length

No mention of varbit(n) and the table doesn't say that bit(n) is acceptable.
So I fixed my script according to this and it works ok now.

L

-- 
Laurent Duperval <mailto:lduperval@microcelli5.com>

Au lieu de tenir des propos teintés de paresse mélangée de fainéantise de
couleur assortie, introduisez une plaque de métal dans l'appareil.
                                          -Léonard le génie





view thread (3+ messages)

Message-ID: <20010515154832.67F7846891@lenard.microcelli5.com>
Permalink:  ../20010515154832.67F7846891@lenard.microcelli5.com/
Also on:    postgresql.org/message-id/20010515154832.67F7846891@lenard.microcelli5.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: lduperval@microcelli5.com, peter_e@gmx.net
  Subject: Re: varbit question
  In-Reply-To: <20010515154832.67F7846891@lenard.microcelli5.com>
  References: <Pine.LNX.4.30.0105151740520.757-100000@peter.localdomain> <20010515154832.67F7846891@lenard.microcelli5.com>

* 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