QualityCentral InterClient entries

IC2.5 does not work under RH linux 7.1 and 7.2

Ed Holdsworth — Fri, 30 Mar 2007 22:55:02 GMT

QC#: 2401 Version: 2.5 Status: Closed defect, no action required Resolution: The bug is no longer relevent Description: IC2.5 under RH7.1/7.2 causes intermittment errors in Jbuilder datapilot when attempting to access data in a table.
Note: connection to

InterClient needs support for IBEvents

Anthony Martin — Fri, 30 Mar 2007 22:52:46 GMT

QC#: 9551 Version: 4.0 Status: Open defect, requires resolution Description: It would be a huge improvement if InterClient directly supported IBEvents in some way.

(Pulled) interbase.interclient.IBTimestamp class needs to support milliseconds

Mon, 12 Feb 2007 17:31:53 GMT

QC#: 40383 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: interbase.interclient.IBTimestamp class needs to support milliseconds

(Pulled) Make InterClient return the time precision stored in the database. Currently it does not return fractional seconds. Seconds

Mon, 12 Feb 2007 17:31:53 GMT

QC#: 40384 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: Make InterClient return the time precision stored in the database. Currently it does not return fractional seconds.
Seconds are stored in the

(Pulled) preparedstatement.getMetaData returns null pointer exception. It should return null at a minimum. Shaunuk is familiar with probl

Mon, 12 Feb 2007 17:31:53 GMT

QC#: 40385 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: preparedstatement.getMetaData returns null pointer exception. It should return null at a minimum. Shaunuk is familiar with problem and has dev ki

(Pulled) Nulls inserted in place of throwing transliteration exception

Mon, 12 Feb 2007 17:31:53 GMT

QC#: 40386 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: Nulls inserted in place of throwing transliteration exception

(Pulled) JDBC3.0 Driver is setting InterBase datatype NUMERIC(5,5) to a java.lang.Long. I think it should be a Java Decimal.

Mon, 12 Feb 2007 17:31:52 GMT

QC#: 40375 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: JDBC3.0 Driver is setting InterBase datatype NUMERIC(5,5) to a java.lang.Long. I think it should be a Java Decimal.

(Pulled) Attempting to create a new index using a generator fails when done programmatically. The error is: "Class: interbase.intercli

Mon, 12 Feb 2007 17:31:52 GMT

QC#: 40376 Version: 3.0 Status: Closed defect, no action required Resolution: Bug description is invalid as submitted Description: Attempting to create a new index using a generator fails when done programmatically. The error is:
"Class: interbase.inte

(Pulled) What is listed below are various bugs which were found by the Kiribati project memebers who are using Borland Application Server

Mon, 12 Feb 2007 17:31:52 GMT

QC#: 40377 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: What is listed below are various bugs which were found by the Kiribati project memebers who are using Borland Application Server 5.x , InterBase

(Pulled) Interbase 6.5 with Interclient 2.5 : I have a table with a TIMESTAMP column. If I look at the table using Interbase Workbench

Mon, 12 Feb 2007 17:31:52 GMT

QC#: 40378 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: Interbase 6.5 with Interclient 2.5 :
I have a table with a TIMESTAMP column. If I look at the table using Interbase Workbench, it says the col

(Pulled) DriverManager.setLogWriter does not output anything when using Interclient. Compare this with JDataStore which is very verbose i

Mon, 12 Feb 2007 17:31:52 GMT

QC#: 40379 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: DriverManager.setLogWriter does not output anything when using Interclient. Compare this with JDataStore which is very verbose in logging SQL sta

(Pulled) ResultSetMetaData calls "isReadOnly" and "isWritable" give back a null pointer error. +++++++++++++++++++++++++++++++++++++

Mon, 12 Feb 2007 17:31:52 GMT

QC#: 40380 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: ResultSetMetaData calls "isReadOnly" and "isWritable" give back a null pointer error.
++++++++++++++++++++++++++++++++++++++++++++++++++
12

(Pulled) resultset.getMetaData().getColumnDisplaySize() returns wrong value for timestamp fields. Type 4 driver returns 1, Type 3 driver

Mon, 12 Feb 2007 17:31:52 GMT

QC#: 40381 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: resultset.getMetaData().getColumnDisplaySize() returns wrong value for timestamp fields. Type 4 driver returns 1, Type 3 driver returns 19. I wou

(Pulled) We cannot use extended properties for interclient driver on JBuilder4. Please see RAID#85458. This bug is same bug. The c

Mon, 12 Feb 2007 17:31:52 GMT

QC#: 40382 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: We cannot use extended properties for interclient driver on JBuilder4.
Please see RAID#85458.
This bug is same bug.
The cause of this bug

Calling stmt.executeBatch(); on a Statement with an "Empty Batch" throws a Null pointer exception.

Craig Stuntz — Fri, 15 Dec 2006 11:03:15 GMT

QC#: 7419 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: Calling stmt.executeBatch(); on a Statement with an "Empty Batch" throws a Null pointer exception.
Marked this Severity 3 because most users won

Statement.cancel() current behavior does not allow for canceling long running SELECT statements.

Craig Stuntz — Fri, 15 Dec 2006 11:03:15 GMT

QC#: 7420 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: 1. Statement.cancel() current behavior does not allow for canceling long running SELECT statements. When a executeQuery is performed in JDBC th

The java.sql.DatabaseMetadata.getImportedKeys() returns space padded values for the FK_NAME column.

Craig Stuntz — Tue, 27 Jun 2006 19:41:02 GMT

QC#: 7421 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: The java.sql.DatabaseMetadata.getImportedKeys() returns space padded values for the FK_NAME column. For example:

"INTEG_17 "

java.sql.DatabaseMetaData.getTypeInfo() does not return a row for java.sql.Types.FLOAT (integer 6)

Craig Stuntz — Tue, 27 Jun 2006 19:41:02 GMT

QC#: 7422 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: java.sql.DatabaseMetaData.getTypeInfo() does not return a row for java.sql.Types.FLOAT (integer 6). However, there are tables in the employee dat

The java.sql.ResultSetMetaData will return 1111 (OTHER) for an array column.

Craig Stuntz — Tue, 27 Jun 2006 19:41:02 GMT

QC#: 7423 Version: 4.0 Status: Closed defect, no action required Resolution: Bug has been fixed Description: The java.sql.ResultSetMetaData will return 1111 (OTHER) for an array column.

SQL Dialect 1 in InterBase7/InterClient type 4 (3.00.12)

hugo kuiper — Wed, 08 Jun 2005 18:09:16 GMT

QC#: 5776 Version: 2.00 Status: Closed defect, no action required Resolution: Need more information/demo/steps Description: I used a database, backed up from IB6 and restored into IB7, but still with SQL Dialect 1.
database.saveChanges(dataSet) gives a

DriverManager.setLogWriter tells you nothing

hugo kuiper — Mon, 21 Feb 2005 12:54:35 GMT

QC#: 5777 Version: 2.00 Status: Open defect, requires resolution Description: I had some problems with Database.saveChanges().
I tried to find a solution by setting:
DriverManager.setLogWriter(new PrintWriter(System.out))
I thought: now I can see what t

Can't use InterClient.Jar file from SP2, ISO8859-1 no longer working

Mikael Nilsson — Mon, 21 Feb 2005 12:51:03 GMT

QC#: 7482 Version: 4.5 Status: Closed defect, no action required Resolution: Need more information/demo/steps Description: 1. I can't tell the vesion number. It's not visible when installing
JDBC Type 4 driver. I'm only guessing when saying 4.5
2. When u

Can connect to a database useing Interclient Communication Diagnostics

Alan Lindsay — Mon, 04 Oct 2004 22:12:23 GMT

QC#: 8272 Version: 2.5 Status: Closed defect, no action required Resolution: Need more information/demo/steps Description:

Uninstall doesn't remove service.

Anthony Martin — Wed, 25 Feb 2004 20:24:57 GMT

QC#: 4671 Version: 2.00 Status: Closed defect, no action required Resolution: The bug is no longer relevent Description: If InterServer is installed as a service, the uninstaller does not 1) stop the service, and 2) remove the service.
This must be done

Russian localized messages displayed incorrectly. (as ?????)

Andrey Aristarkhov — Wed, 25 Feb 2004 20:23:53 GMT

QC#: 1482 Version: 2.00 Status: Closed defect, no action required Resolution: The bug is no longer relevent Description: It looks like Resources_ru.class in interbase.interclient and interbase.interclient.utils packges was compiled with incorrect encoding