Message-ID: <3B409F8F.7050408@xythos.com>
Date: Mon, 02 Jul 2001 09:21:35 -0700
From: Barry Lind <barry@xythos.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010628
MIME-Version: 1.0
To: Arsalan Zaidi <azaidi@directi.com>
CC: PostgreSQL jdbc list <pgsql-jdbc@postgresql.org>,
	Bruce Momjian <pgman@candle.pha.pa.us>
Subject: Re: [INTERFACES] New code for JDBC driver
References: <200106301642.f5UGgkj14915@candle.pha.pa.us>
	<3B3E7A94.209@xythos.com>
	<00b801c102c4$fdd49ea0$4301a8c0@directi.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Arsalan,

Why do you consider semi colons outside of quotes to be an error condition?

It is legal under postgresql to execute multiple SQL statements under 
one call to the server.  For example you can execute:

update foo set bar = ?; select * from foo;

In one call to the server by setting the 'query' on the Statement or 
Prepared statement object to be the entire string above.

As you can see from this example it is certainly therefore legal to have 
a semi-colon outside of quotes.

As to your second point about escapeSQL escaping quotes, I don't see 
anywhere in the JDBC spec that says that type of behavior is supposed to 
happen.  Do you have an example where you feel the behavior of the 
escapeSQL method isn't conforming to the JDBC spec with regards to quote 
handling?

thanks,
--Barry