Received: from p1.selectacast.net (IDENT:root@p1.selectacast.net [206.41.1.251]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA17917 for ; Mon, 29 May 2000 22:36:23 -0400 (EDT) (envelope-from jks@selectacast.net) Received: from selectacast.net (IDENT:jks@d1 [209.219.91.66]) by p1.selectacast.net (8.9.3/8.9.3) with ESMTP id WAA25674; Mon, 29 May 2000 22:36:16 -0400 Message-ID: <39332920.4C9BC95B@selectacast.net> Date: Mon, 29 May 2000 22:36:16 -0400 From: Joseph Shraibman Organization: Xtenit X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.15 i686) X-Accept-Language: en MIME-Version: 1.0 To: Gunnar R|nning CC: Janossy Gergely , pgsql-interfaces@postgresql.org Subject: Re: jdbc driver: Why it isn't jdbcCompliant? References: <00052701341103.02227@azul> <3932BC0A.482A765B@selectacast.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200005/82 I wasn't making a point. I was just including the comment from the source code to tell why jdbcCompliant() returns false, namely that postgresql isn't sql 92 compliant. Gunnar R|nning wrote: > > Joseph Shraibman writes: > > Yes - your point being ? I think that you will find that most JDBC drivers > out there do not implement the spec. to the letter. But using good OO > design principles and adapters you can easily use a subset of the spec(plus > your favorite non SQL 92 database extensions) together with appropriate > adaptors to keep things fairly easy to port between databases. The four > databases that I know best Sybase ASE, PosgreSQL, Progress V9.1 and MySQL > do not fully implement the JDBC spec. But then again I think SQL 92 is the > same story... > > Regards, > > Gunnar > > > >From the Driver source code: > > > public boolean jdbcCompliant() > > { > > return false; > > }