You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (Jira)" <ji...@apache.org> on 2019/12/30 13:56:00 UTC

[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0

    [ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005327#comment-17005327 ] 

Bryan Pendleton commented on DERBY-7063:
----------------------------------------

See : [https://stackoverflow.com/a/57221011/193453]

 

Have you tried adding derbyshared.jar as an additional jar file in your Squirrel driver configuration?

 

Where do you recommend we should document this new behavior? It is documented here: [http://db.apache.org/derby/releases/release-10.15.1.3.cgi]

 

Note that if you are running Java 1.8, you can also consider just using Derby 10.14, rather than Derby 10.15.

> Cannot connect using squirrel 3.3.0
> -----------------------------------
>
>                 Key: DERBY-7063
>                 URL: https://issues.apache.org/jira/browse/DERBY-7063
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Server
>    Affects Versions: 10.15.1.3
>            Reporter: sagar
>            Priority: Major
>
> The derbyclient.jar file does not have the org.apache.derby.jdbc.ClientDriver.class
>  
> When I add the jar file in squirrel, ssquirrel automatically detects the driver but since this class is missing it does not detect it.
> Till now I was using 10.11.1.1 database. Now I have decided to upgrade and this issue cropped up.
>  
> Yes Derby has switched to the module system from 10.15.1.3 but the derby documentation mentions connection to Network Server similar to previous as using the 
> org.apache.derby.jdbc.ClientDriver and this class is missing from the new derbyclient.jar.
>  
>  
> Squirrel is running on Java 1.8



--
This message was sent by Atlassian Jira
(v8.3.4#803005)