Issue Details (XML | Word | Printable)

Key: DERBY-410
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Philip Wilder
Reporter: Kathey Marsden
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Derby

ClientDataSource should not require serverName/portNumber to be set

Created: 30/Jun/05 06:39 AM   Updated: 26/Jan/06 02:00 AM
Return to search
Component/s: JDBC
Affects Version/s: 10.1.1.0, 10.2.1.6
Fix Version/s: 10.1.1.0, 10.1.2.1

Time Tracking:
Not Specified

Resolution Date: 18/Sep/05 12:07 AM


 Description  « Hide
the ClientDataSource property serverName should default to "localhost" but is currently required.

http://incubator.apache.org/derby/docs/adminguide/cadminappsclient.html

See repro for DERBY-409

and comment out the lines
ds.setServerName("localhost");
ds.setPortNumber(1527);



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Philip Wilder made changes - 30/Jun/05 11:57 PM
Field Original Value New Value
Assignee Philip Wilder [ acadia_student_01 ]
Philip Wilder made changes - 01/Jul/05 01:57 AM
Status Open [ 1 ] In Progress [ 3 ]
Philip Wilder added a comment - 07/Jul/05 04:35 AM
Please see DERBY-406 for an update on the status of this issue.

Repository Revision Date User Message
ASF #219980 Thu Jul 21 01:52:49 UTC 2005 bandaram Merge trunk change 209498 to 10.1 branch.

DERBY-406 - Sets the username to start with the default value ("APP")
DERBY-410 - Sets the server name to start with the default value ("localhost")
DERBY-409 - Adds a semi-colon in the connection class to avoid databasenames like myDBcreate=true resulting from no dividing semi-colon.

Submitted by Satheesh Bandaram (satheesh@sourcery.org)
Files Changed
MODIFY /incubator/derby/code/branches/10.1/java/testing/org/apache/derbyTesting/functionTests/master/DerbyNetClient/dataSourcePermissions_net.out
MODIFY /incubator/derby/code/branches/10.1/java/client/org/apache/derby/jdbc/ClientBaseDataSource.java
MODIFY /incubator/derby/code/branches/10.1/java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/dataSourcePermissions_net.java
MODIFY /incubator/derby/code/branches/10.1/java/client/org/apache/derby/client/am/Connection.java

Satheesh Bandaram added a comment - 21/Jul/05 11:01 AM
Ported this fix from trunk to 10.1 release with change: 209498

Mike Matrigali made changes - 17/Aug/05 08:29 AM
Component/s JDBC [ 11407 ]
Philip Wilder added a comment - 16/Sep/05 03:21 AM
Freeing this issue to anyone else who sees a way in which Dan's concerns about a lack of prior behaviour can be addressed.

(See DERBY-406)

Philip Wilder made changes - 16/Sep/05 03:21 AM
Status In Progress [ 3 ] Open [ 1 ]
Philip Wilder made changes - 16/Sep/05 03:21 AM
Assignee Philip Wilder [ acadia_student_01 ]
Philip Wilder added a comment - 18/Sep/05 12:07 AM
The July 6, patch addressed the original concerns of this issue. While Dan brought up the potential issue of null handling (See Derby-406) further investigations appear to indicate null values are handled appropriately.

Philip Wilder made changes - 18/Sep/05 12:07 AM
Status Open [ 1 ] Resolved [ 5 ]
Fix Version/s 10.1.1.0 [ 10993 ]
Resolution Fixed [ 1 ]
Fix Version/s 10.1.2.0 [ 12310270 ]
Assignee Philip Wilder [ acadia_student_01 ]
Deepa Remesh made changes - 30/Sep/05 02:52 AM
Fix Version/s 10.1.1.1 [ 12310332 ]
Kathey Marsden made changes - 26/Jan/06 02:00 AM
Status Resolved [ 5 ] Closed [ 6 ]