[
https://issues.apache.org/jira/browse/IGNITE-8148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16433827#comment-16433827
]
ASF GitHub Bot commented on IGNITE-8148:
----------------------------------------
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3794
IGNITE-8148
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8148
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3794.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3794
----
commit 97b7a5ec172a1bb8fa5ca05d56255d1b44411d57
Author: devozerov <vozerov@...>
Date: 2018-04-11T12:06:21Z
Done.
commit 421494724879d14ba1694f91c50f4f3864d829ee
Author: devozerov <vozerov@...>
Date: 2018-04-11T12:21:58Z
Tests.
----
> JDBC thin driver: use semicolon as parameter's delimiter
> --------------------------------------------------------
>
> Key: IGNITE-8148
> URL: https://issues.apache.org/jira/browse/IGNITE-8148
> Project: Ignite
> Issue Type: Task
> Components: jdbc
> Affects Versions: 2.4
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Major
> Fix For: 2.5
>
>
> Currently we split JDBC parameters using ampersand. This causes a number of
> usability concerns with escaping, especially when it is needed to pass
> connection URL to command line (e.g. sqlline in bash or PowerShell). A number
> of other vendors use either parentheses or semicolon as a delimiter. I
> propose to choose semicolon.
> Also it is necessary to make sure that old-style connection URLs work fine
> after this change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
