[eclipselink-dev] Review request: EL Bug 469182

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[eclipselink-dev] Review request: EL Bug 469182

From: David Minsky <david.minsky@xxxxxxxxxx>
Date: Tue, 02 Jun 2015 17:28:28 -0400
Delivered-to: eclipselink-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-dev>
List-help: <mailto:eclipselink-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=unsubscribe>
Organization: Oracle Corporation
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

EclipseLink Developers,

Bug 469182 - Using coalesce() in JPQL with a null parameter value sets incorrect type on jdbc statement setNull call
https://bugs.eclipse.org/bugs/show_bug.cgi?id=469182

I would be grateful if someone would be kind enough to take 5-10 minutes to review the above bug for checkin -> 2.7 & 2.6. Pretty straightforward testcase & fix, the issue is with EL internally configuring a default parameter (untyped) from a coalesce() function in JPQL, which causes an issue in JDBC when executing such a query with a null parameter. More details & small code example in the bug.

Testing: JPA regression suites pass as expected on Oracle & MySQL.

Many thanks,

-David

Prev by Date: Re: [eclipselink-dev] Review request: Bug 464088
Next by Date: [eclipselink-dev] Review request: EL Bug 469642
Previous by thread: [eclipselink-dev] Review request: Bug 464088
Next by thread: [eclipselink-dev] Review request: EL Bug 469642
Index(es):
- Date
- Thread

Breadcrumbs