Re: pg_dump and boolean format

From: Michael Glaesemann <grzm(at)seespotcode(dot)net>
To: Scott Frankel <frankel(at)circlesfx(dot)com>
Cc: PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump and boolean format
Date: 2010-08-11 17:12:38
Message-ID: 13572A4A-2495-404C-BC3F-95DB37705A9F@seespotcode.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Aug 11, 2010, at 13:00 , Scott Frankel wrote:

> The pg docs say that booleans can be stored as 't', 'true', 'y', 'yes', or '1'.

Booleans are not "stored" as those literals: those are only acceptable literals (i.e., string representations) for boolean values.

> I'm using pg_dump to create an SQL script for importing into another database. This will happen automatically and repeatedly. Unfortunately, the other database (sqlite) is limited to only integer representation of booleans: 0 or 1.

One option is to use COPY to export the data in a format you like. For example: COPY (SELECT CAST(boolean_column AS INT) FROM my_table) TO STDOUT. Then write a script which reads the exported data files and loads them into your sqlite database. COPY WITH CSV would likely be helpful as well.

Michael Glaesemann
grzm seespotcode net

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael C Rosenstein 2010-08-11 17:17:48 PG-friendly CASE/modeling tool?
Previous Message Bruce Momjian 2010-08-11 17:12:13 Re: Finding last checkpoint time