How would 'ignore' and 'false' differ? Also, your naming would presumably restrict the property to just JPQL. What about a broader toggle to control strict JPA compliance? It seems like if someone wants strict compliance, they're going to want it everywhere, not just in JPQL.
-Patrick On Jan 15, 2008 8:05 PM, Pinaki Poddar <[EMAIL PROTECTED]> wrote: > openjpa.jpql.Extensions : true|false|ignore|warn > > > -----Original Message----- > From: Patrick Linskey [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 15, 2008 10:03 PM > To: [email protected] > Subject: JPQL extensions > > Hi, > > Earlier today, I modified the JPQL parser to allow some extensions to > JPQL. I expect that there is other non-standard extended behavior (JPQL > and otherwise) in OpenJPA. It seems like it might be desirable to have a > property that controls whether or not OpenJPA allows extended behavior. > > I was thinking that a property like so could be useful: > > openjpa.JPAExtensions: true | false | warn > > Thoughts? > > -Patrick > > -- > Patrick Linskey > 202 669 5907 > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual or > entity named in this message. If you are not the intended recipient, and have > received this message in error, please immediately return this by email and > then delete it. > -- Patrick Linskey 202 669 5907
