From: | Barry Lind <blind(at)xythos(dot)com> |
---|---|
To: | Fernando Nasser <fnasser(at)redhat(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: setMaxFieldSize |
Date: | 2003-06-23 16:05:01 |
Message-ID: | 3EF7252D.4050008@xythos.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Fernando,
No reason that I can think of. That code predates my involvement.
thanks,
--Barry
Fernando Nasser wrote:
> Can you someone tell me why we do not implement this? The comment does
> not explain why the "NOT!".
>
> All we have to do is to properly truncate the received values. If this
> is a good programming practice or not it is debatable, but it is in the
> JDBC standard anyway. It may even be useful for some applications out
> there.
>
>
> /*
> * Sets the maxFieldSize - NOT! - We throw an SQLException just
> * to inform them to stop doing this.
> *
> * @param max the new max column size limit; zero means unlimited
> * @exception SQLException if a database access error occurs
> */
> public void setMaxFieldSize(int max) throws SQLException
> {
> throw new PSQLException("postgresql.stat.maxfieldsize");
> }
>
From | Date | Subject | |
---|---|---|---|
Next Message | Fernando Nasser | 2003-06-23 16:36:55 | Re: setMaxFieldSize |
Previous Message | scott.marlowe | 2003-06-23 14:07:06 | Re: maxconnection |