From: David Hartwig <daveh@insightdist.com>
To: PostgreSQL-development <hackers@postgreSQL.org>
Cc: pgsql-interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Bytea(precision)
Date: Mon, 07 Dec 1998 13:52:48 -0500
Message-ID: <366C23FF.BD3C333E@insightdist.com> (raw)
Recently, while testing the application compatibility of the ODBC driver
in , we have come across a problem. Some applications, specifically
MS Project, want to create tables using a bounded binary data type.
(i.e. SQL_BINARY) Up to now, we have mapped ODBC's SQL_BINARY to
PostgreSQL's BYTEA. The problem is that when the application tries to
create the table. Example:
CREATE TABLE foo (bar BYTEA(100));
PostgreSQL errors, complaining about the "(". I have created a
patch, which I am now testing, to allow this syntax for BYTEA. It also,
truncates to the specified precision in the same fashion as does VARCHAR
while preserving its original behavior when a precision is not
specified.
1. Are there any objections?
2. It is very light weight and I would like to get the patch into
6.4.1. Is this possible? (I do not know the plans for this 6.4.1)
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: daveh@insightdist.com, hackers@postgreSQL.org
Subject: Re: Bytea(precision)
In-Reply-To: <366C23FF.BD3C333E@insightdist.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