Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipselink-dev] bug 327225 - MaxDB: JPQL date/time functions current_date, current_time are not mapped properly

Hi all,
besides implementing the current_date/time/timestamp functions properly in the MaxDB platform, I am proposing to adjust the following test
--- foundation/eclipselink.core.test/src/org/eclipse/persistence/testing/tests/expressions/ (revision 8333)
+++ foundation/eclipselink.core.test/src/org/eclipse/persistence/testing/tests/expressions/ (working copy)
@@ -191,7 +191,7 @@
     protected void _addCurrentDateTest() {
         ExpressionBuilder builder = new ExpressionBuilder();
-        _expression_ _expression_ = builder.get("period").get("startDate").lessThan(builder.currentDate());
+        _expression_ _expression_ = builder.get("period").get("startDate").lessThan(builder.currentDateDate());
Employee.period.startDate has the type java.sql.Date and hence the currentDateDate() method (corresponding to current_date in JPQL) should be used, I think. And MaxDB thinks so as well ;-).
OK if I proceed with this change?
Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Léo Apotheker (stellvertretender Sprecher/Deputy CEO), Werner Brandt, Claus Heinrich, Gerhard Oswald, John Schwarz, Peter Zencke
Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner
Registergericht/Commercial Register Mannheim No HRB 350269

Back to the top