ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-4347) ODBC: NPE when cache name is different from the one configured in DSN
Date Wed, 30 Nov 2016 23:47:59 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Denis Magda updated IGNITE-4347:
--------------------------------
    Attachment: exception.png

> 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
(v6.3.4#6332)

Mime
View raw message