--
You received this message because you are subscribed to the Google Groups "Querydsl" group.
To unsubscribe from this group and stop receiving emails from it, send an email to querydsl+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi.This behaviour won't change with the 4.0.0 release, and will be present in all 4.* releases for backwards compatibility.Timo
Thanks! Also, is there any reason JPAQuery's clone(JPAQuery) method is protected? I'm trying to override clone(), but that requires me calling super.clone(). When I call it, I get back an object of type JPAQuery. I need to then return a CustomJPAQuery object. If I could access clone(JPAQuery) I could just do this.clone(super.clone()), but I can't access it.
On Wednesday, April 22, 2015 at 2:25:10 PM UTC-4, timowest wrote:
Hi.This behaviour won't change with the 4.0.0 release, and will be present in all 4.* releases for backwards compatibility.Timo
On Wed, Apr 22, 2015 at 9:22 PM, Michael Tontchev via Querydsl <querydsl+APn2wQeUt6jEuBVj9FETOEr...@googlegroups.com> wrote:I notice that all of the above classes, when they have methods called from them to build a query, modify the current object and then return it. Is it guaranteed that this will remain so? That is, that the methods will always modify the current object instead of creating a new query to modify.--For example, say you doJPAQuery q = new JPAQuery(em);q.from(user).where(user.name.eq("Ted"));that from() call modifies q. Same with the where() call. But they also return a JPAQuery object. Are we guaranteed that they will always return the current object? Or is it possible that in the future you might decide to make each call return a new object, leaving the original q unchaged?(Of course, disregard this question as it regards the clone() methods).I'm trying to extend the classes mentioned above, but if new objects are returned, I'd need to call clone(JPAQuery), which is protected and I can't access. (And the update clause and delete clause don't have clone()).Thanks!
You received this message because you are subscribed to the Google Groups "Querydsl" group.
To unsubscribe from this group and stop receiving emails from it, send an email to querydsl+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi,It is an implementation detail that callers don't have to worry about (it's somewhat like a copy constructor, but not a contructor).Protected members are visible by subclasses, so what exactly doesn't work?Best regards,Ruben
On Wed, 22 Apr 2015 20:40:14 +0200, Michael Tontchev via Querydsl <querydsl+APn2wQeUt6jEuBVj9FETOEr34G61O6V5VHz2H2bqynp57dsdUszLXiT@googlegroups.com> wrote:
Thanks! Also, is there any reason JPAQuery's clone(JPAQuery) method is protected? I'm trying to override clone(), but that requires me calling super.clone(). When I call it, I get back an object of type JPAQuery. I need to then return a CustomJPAQuery object. If I could access clone(JPAQuery) I could just do this.clone(super.clone()), but I can't access it.
On Wednesday, April 22, 2015 at 2:25:10 PM UTC-4, timowest wrote:
Hi.This behaviour won't change with the 4.0.0 release, and will be present in all 4.* releases for backwards compatibility.Timo
On Wed, Apr 22, 2015 at 9:22 PM, Michael Tontchev via Querydsl <querydsl+APn2wQeUt6jEuBVj9FETOEr34G61O6V5VHz2H2bqynp57dsdUszLXiT@googlegroups.com> wrote:I notice that all of the above classes, when they have methods called from them to build a query, modify the current object and then return it. Is it guaranteed that this will remain so? That is, that the methods will always modify the current object instead of creating a new query to modify.--For example, say you doJPAQuery q = new JPAQuery(em);q.from(user).where(user.name.eq("Ted"));that from() call modifies q. Same with the where() call. But they also return a JPAQuery object. Are we guaranteed that they will always return the current object? Or is it possible that in the future you might decide to make each call return a new object, leaving the original q unchaged?(Of course, disregard this question as it regards the clone() methods).I'm trying to extend the classes mentioned above, but if new objects are returned, I'd need to call clone(JPAQuery), which is protected and I can't access. (And the update clause and delete clause don't have clone()).Thanks!
You received this message because you are subscribed to the Google Groups "Querydsl" group.
To unsubscribe from this group and stop receiving emails from it, send an email to querydsl+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.