Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360486 - Inconsistency between SQLDataSource and java.sql.Connection
Summary: Inconsistency between SQLDataSource and java.sql.Connection
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-10 17:26 EDT by Paul Hoffman CLA
Modified: 2017-02-23 14:19 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Hoffman CLA 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 CLA 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 CLA 2011-10-17 14:52:48 EDT 
verified, closed