ASF GitHub Bot commented on IGNITE-4347:

GitHub user isapego opened a pull request:


    IGNITE-4347: Fixed NPE.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/isapego/ignite ignite-4347

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1305
commit 6633904bc28b8d47b16588b1a3dff84922c21efb
Author: Igor Sapego <isap...@gridgain.com>
Date:   2016-12-01T11:55:42Z

    IGNITE-4347: Fixed NPE.


> ODBC: NPE when cache name is different from the one configured in DSN
> ---------------------------------------------------------------------
>                 Key: IGNITE-4347
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4347
>             Project: Ignite
>          Issue Type: Bug
>          Components: odbc
>            Reporter: Denis Magda
>            Assignee: Igor Sapego
>            Priority: Critical
>             Fix For: 1.8
>         Attachments: exception.png
> The following query was executed from PHP PDO side
> {code}
> $dbs = $dbh->prepare('INSERT INTO Person (_key, firstName, lastName, resume, 
> salary) 
>         VALUES (?, ?, ?, ?, ?)');
> {code}
> The cache name in Spring XML configuration was "Person" while the DSN was 
> configured to use "PersonCache" as a default cache name.
> As a result, I was getting NPE shown in the attached screenshot. Only after I 
> sorted out the root cause of the NPE referring to the source code I could 
> finally fix the issue.
> Let's provide more meaningful explanation rather than throwing NPE saying 
> something like "The cache named {cache_name} has not been found. Make sure 
> that ODBC connection string or DSN is configured properly."

This message was sent by Atlassian JIRA

Reply via email to