Bytea(precision)

From: David Hartwig <daveh(at)insightdist(dot)com>
To: PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Cc: pgsql-interfaces <pgsql-interfaces(at)postgreSQL(dot)org>
Subject: Bytea(precision)
Date: 1998-12-07 18:52:48
Message-ID: 366C23FF.BD3C333E@insightdist.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

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)

Browse pgsql-hackers by date

  From Date Subject
Next Message David Hartwig 1998-12-07 19:19:18 Cursor Movement - Past the End
Previous Message Oleg Broytmann 1998-12-07 17:40:31 Re: [HACKERS] Date/time on glibc2 linux

Browse pgsql-interfaces by date

  From Date Subject
Next Message David Hartwig 1998-12-07 19:19:18 Cursor Movement - Past the End
Previous Message Constantin Teodorescu 1998-12-07 15:26:15 PgAccess stable version 0.92 released !