Our developers are getting the following error posted from several Java
applications.
[Microsoft][SQLServer 2000 Driver for JDBC] Invalid operation for the
current cursor position
Is anyone familiar with this error?
It can occur when you try to access result set data without ever
having called next(). If you can show us the whole original stack trace
of the exception and the code that caused it, we can probably see the problem.
Joe Weinstein at BEA Systems
Re: Possible Type Conversion Defect ... Specifically we are breaking due to the lack of conversion from BIGINT to ... Microsoft SQL Server 2000 JDBC driver.... I'll agree that the JDBC API specifications could be a bit more precise. ... a JDBC driver attempts to convert the underlying data to the Java... (microsoft.public.sqlserver.jdbcdriver)
Re: Ora10 JDBC Driver with TIMESTAMP WITH LOCAL TIME ZONE ... >> Robert Klemme wrote: ... >>> driver is the newest driver for Ora 10.2. ... >>> JDBC driver I suspect it's a JDBC driver issue. ... > sets the session time zone of the connection and saves the session ... (comp.databases.oracle.misc)
Re: federate several datasources ... >>I want to federate several physical datasources, ... >>its JDBC driver.... >>My idea is that this aggregator could be implemented as a special JDBC...open-source databases such as MySQL, PostGreSQL, but this is outside the ... (comp.lang.java.databases)
RE: New JDBC 1.2 driver runs slower than JDBC 1.1; my db definition ... New JDBC 1.2 driver runs slower than JDBC 1.1; ...[PersonGID]... While we did not specifically target performance with the v1.2 driver beyond the Adapative Buffering changes, I am surprised that you are seeing slower ... it looks like both your SELECT and UPDATE statement are restricted to a single table. ... (microsoft.public.sqlserver.jdbcdriver)
Re: MS SQL Server 2005 JDBC Driver Performance Issue ... On to the v1.1 driver!... You will now be able to tweak the PacketSize (TDS buffer that you use ... will use more memory but be much faster) in these scenarios.... Shame on Microsoft and Sybase for writing such badly performing JDBC... (microsoft.public.sqlserver.jdbcdriver)
