Skip site navigation (1) Skip section navigation (2)


From: "Vilson farias" <vilson(dot)farias(at)digitro(dot)com(dot)br>
To: "Paolo Sinigaglia" <sini(at)informativesystem(dot)it>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: VARCHAR and TEXT
Date: 2001-03-29 16:48:07
Message-ID: 001901c0b870$08410260$ (view raw or whole thread)
Lists: pgsql-general
I gave up from using ODBC... to much problems with blobs and other stuff...
and really very low speed under Delphi. Try Zeos Database Components for
Postgre( I've been using for 6 mounths and its
great. Blobs greater than 8Kb still are a big problem, but you will see this
component can recognize text fields as Memo and OIDs as Binary Blobs.

A really good point of these components is that you dont need BDE or ODBC
(everything is done accessing a single dll). My apps are very small and
installation is a piece of cake.

My config : Zeos 3.0.8 under Delphi 5 Enterprise.


José Vilson de Mello de Farias
Dígitro Tecnologia Ltda - Brazil

----- Original Message -----
From: Paolo Sinigaglia <sini(at)informativesystem(dot)it>
To: <pgsql-general(at)postgresql(dot)org>
Sent: Quinta-feira, 29 de Março de 2001 11:53

: Hi everybody,
: I have a little question about string types in PostgreSQL: it seems I
: understood well how string data are stored in the database, from a recent
: post by Tom Lane I feel encouraged to think that VARCHAR and TEXT are
: treated the same way by PG, i.e. they occupy ony the space needed by their
: actual length, bt I'm not so sure of it.
: I ask this because I'm trying using PG as database server in a project
: developed in delphi under ms-win and it seems to me that varchar and text
: fields are not treated the same way by odbc interface and/or bde (borland
: database engine, the database interface layer used by delphi programs).
: I connect to a table the fields of type VARCHAR are seen as strings while
: the fields of type TEXT are seen as blobs, and this is a little upsetting,
: because some useful functions are not implemented for blob fields.
: I have several tables with fields that could contain quite lengthy
: but usually don't. So I don't want to define theese fields as VARCHAR(400)
: if this means a disk occupation of 400 bye or so for each row (I have some
: 500000 rows in a table and the average length of the field in question is
: about 30, but the max length is near 400).
: Can someone clarify this point?
: Thanks in advance
: ___________________PS
: ---------------------------(end of broadcast)---------------------------
: TIP 3: if posting/reading through Usenet, please send an appropriate
: subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
: message can get through to the mailing list cleanly

In response to

pgsql-general by date

Next:From: Tom LaneDate: 2001-03-29 17:00:35
Subject: Re: Pgsql-7.1RC1: SET SEED = <something>
Previous:From: Tom LaneDate: 2001-03-29 16:43:43
Subject: Re: [SQL] inconsistent functionality with LIKE operator

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group