Re: VARCHAR and TEXT
От | Vilson farias |
---|---|
Тема | Re: VARCHAR and TEXT |
Дата | |
Msg-id | 001901c0b870$08410260$98a0a8c0@dti.digitro.com.br обсуждение исходный текст |
Ответ на | VARCHAR and TEXT ("Paolo Sinigaglia" <sini@informativesystem.it>) |
Список | 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(http://www.marms.com/zeos). 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. Regards, José Vilson de Mello de Farias Dígitro Tecnologia Ltda - Brazil ----- Original Message ----- From: Paolo Sinigaglia <sini@informativesystem.it> To: <pgsql-general@postgresql.org> Sent: Quinta-feira, 29 de Março de 2001 11:53 Subject: [GENERAL] VARCHAR and TEXT : Hi everybody, : I have a little question about string types in PostgreSQL: it seems I don't : 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). When : 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 strings, : 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@postgresql.org so that your : message can get through to the mailing list cleanly :
В списке pgsql-general по дате отправления: