Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Message-ID: <3F8B73B8.9060002@backstagetech.com.au>
Date: Tue, 14 Oct 2003 13:55:36 +1000
From: Scott Eade <seade@backstagetech.com.au>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4.1) Gecko/20031008
MIME-Version: 1.0
To: Torque Developers List <torque-dev@db.apache.org>
Subject: PostegreSQL datatype mapping for LONGVARCHAR -  bytea vs text
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Is there a reason why LONGVARCHAR maps to "bytea" rahter than "text" for 
PostgreSQL?

I am in the process of converting an application over from MySQL to 
PostgreSQL and am finding that my application experiences a couple of 
problems storing data into the columns defined as bytea (usually it just 
hangs).  I am attempting to make my application as database neutral as 
possible (beween MySQL and PostgreSQL that is), and I am thus thinking 
that the PostgreSQL text type would be a better mapping for 
LONGVARCHAR.  So should the PostgreSQL mapping for LONGVARCHAR be 
updated to be "text" or should I switch to CLOB (which uses "text" for 
PostgreSQL and "LONGTEXT" for MySQL)?

Is anyone using a column type that maps to bytea under PostgreSQL 
successfully?  This includes: LONGVARCHAR, BINARY, VARBINARY and 
LONGVARBINARY.

The mapping for LONGVARCHAR looks wrong to my eyes - I'll change it to 
"text" locally and see how things go.

Scott

-- 
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org