Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360486

Summary:	Inconsistency between SQLDataSource and java.sql.Connection
Product:	z_Archived	Reporter:	Paul Hoffman <hoffmanp>
Component:	EDT	Assignee:	Project Inbox <edt.language-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	jvincens
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Paul Hoffman

2011-10-10 17:26:52 EDT

Most of the methods supported by SQLDataSource appear to correspond to a subset of methods in the java.sql.Connection interface.

One of the methods is not a one-to-one mapping.   The Connection isValid(int) method returns a boolean value.   The SQLDataSource isValid(int) returns nothing.
Is this intentional?

Other design questions:

Why were isClosed() and isReadOnly() included, but not close() and setReadOnly()?

Comment 1 Joseph Vincens

2011-10-11 14:32:35 EDT

isValid was wrong and now returns a boolean.
There is a CLOSE action talked about in the spec but it doesn't have its own section.
Tim did not want me to implement setReadOnly.

Comment 2 Paul Hoffman

2011-10-17 14:52:48 EDT

verified, closed