Re: Column size BUG with text/bytea with 7.4 JDBC Driver
| От | Kris Jurka |
|---|---|
| Тема | Re: Column size BUG with text/bytea with 7.4 JDBC Driver |
| Дата | |
| Msg-id | Pine.BSO.4.56.0404102033260.30692@leary.csoft.net обсуждение исходный текст |
| Ответ на | Column size BUG with text/bytea with 7.4 JDBC Driver (build 213) ("j.random.programmer" <javadesigner@yahoo.com>) |
| Ответы |
Re: Column size BUG with text/bytea with 7.4 JDBC Driver (build 213)
|
| Список | pgsql-jdbc |
On Wed, 7 Apr 2004, j.random.programmer wrote: > The latest JDBC driver (build 213) has a serious > bug for the "COLUMN_SIZE" value, obtained via > DBMetaData, getColumns() and then "COLUMN_SIZE. > > The column size returned for both bytea and text > types is -1. > > postgres _should_ return the max col size which > for bytea is about 1 GB (or is it 4 GB theoretically) > For bytea 1GB would be a reasonable limit, but for text it is more difficult to say what the maximum size is because the maximum size for varchar fields is measured in the number of characters, not the number of bytes. The 1GB limit is a byte count limit, not a character count limit, so what would you recommend returning in the presence of a non single byte encoding? Kris Jurka
В списке pgsql-jdbc по дате отправления: