From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
---|---|
To: | Finn Lassen <dcio(at)AxiomInt(dot)com> |
Cc: | Postgresql ODBC List <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Need help with Visual Basic 6 and PostgreSQL |
Date: | 2007-11-24 02:09:23 |
Message-ID: | 406387.75407.qm@web31804.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
--- On Fri, 11/23/07, Finn Lassen <dcio(at)AxiomInt(dot)com> wrote:
> I don't understand the difference between "LongVarchar" and
> "Varchar",
> but I have to use B1 whether I use the ANSI or UNICODE driver.
> (Content of the memo field I put into text data type can be more than
> 64K, so I choose 128000. The default is 8196, so it has to be increased.)
For what it is worth, Postgresql has a 1 Gb limit on the size of a text field. So if you know that you ascii chars are 8 bits, then you should be able to store a little over 134,000,000 characters.
> Conclusion: Version 8.2.4.0 of psqlodbc30a.dll and psqlodbc30w.dll
> require tables WITH OID.
> (The "OID Options, Show column" -- and presumably
> "ShowOidColumn" -- has
> no effect.)
I will try to spend some time to play with ADO record sets without using a DSN to see what happens and see with I can come up with. But in the mean time at least you can perform your test comparison.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-24 02:25:39 | Re: Need help with Visual Basic 6 and PostgreSQL |
Previous Message | Finn Lassen | 2007-11-24 01:55:46 | Re: Need help with Visual Basic 6 and PostgreSQL |