Pinaki: Thanks for the reference. I'd read your article earlier but I didn't understand the implications of that section. I need some additional time to ponder the full implications of this capability and to decide whether or not this provides sufficient power for extending JPQL. But I am immediately concerned that this hides invocation of native functionality in a rather unexpected place. I doubt that I am the first to raise this objection. What persuaded the committee to accept this syntax?
-=- Jerry On Jun 3, 2010, at 2:37 PM, Pinaki Poddar [via OpenJPA] wrote: > > This is a significant weakness of JPA in my not so humble opinion. I would > > love to see a mechanism in JPA > 3.0 which allows the author to define > > aliases within JPQL for stored procedures, SQL functions, or > > DB-specific functions. > > Part of this limitation has been answered with JPA 2.0 itself. In JPA 2.0, > queries can use database specific functions [1]. > > [1] http://www.ibm.com/developerworks/java/library/j-typesafejpa/#N10B02 > See the subsection "Extensible datastore expressions" > > Pinaki > > > View message @ > http://openjpa.208410.n2.nabble.com/JPA-for-portable-database-management-tp5134215p5136374.html > > To start a new topic under OpenJPA Users, email > [email protected] > To unsubscribe from OpenJPA Users, click here. > -- View this message in context: http://openjpa.208410.n2.nabble.com/JPA-for-portable-database-management-tp5134215p5136436.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
