On Fri, Nov 2, 2012 at 12:56 PM, Xybrek <xyb...@gmail.com> wrote:
> Is it possible to build a Query object with Objectify with a query
> string? I mean, I know Objectify builds queries like:
I've done parsers in the past but that was with C++, but I can consider doing this. Also, I am pretty sure that SQL-like queries may not be much suitable for building query objects. I may need to fully understand the full extent feature of the Query class, the depth and the full list of possible query combinations. I find this idea really fun, not considering that we really need this for our project coz' we have a system that is built on triggering SQL scripts in the backend, and we need to reuse it with our AppEngine port of the system.
While thinking of doing this feature, for me to move on with our project, is it possible that JPA and Objectify to work together, that is persisted Entities using Objectify be queried by JPA and vice versa?
You should have no trouble using JPA and Objectify in the same project as
long as you keep the entity classes in sync. Although, if you are going to
go through that trouble, why not just use JPA?
The only major impedance mismatches will be polymoprhism, some edge cases
in @Embed collections (specifically null handling), and partial indexes
(which don't exist in JPA).
On Fri, Nov 2, 2012 at 4:37 PM, Xybrek <xyb...@gmail.com> wrote:
> While thinking of doing this feature, for me to move on with our project,
> is it possible that JPA and Objectify to work together, that is persisted
> Entities using Objectify be queried by JPA and vice versa?
> On Saturday, November 3, 2012 1:41:41 AM UTC+8, Jeff Schnitzer wrote:
>> There is not currently any plan. If you want to build some sort of
>> parser, we might consider including it... but this is a nontrivial feature.
>> On Fri, Nov 2, 2012 at 12:56 PM, Xybrek <xyb...@gmail.com> wrote:
>>> Is it possible to build a Query object with Objectify with a query
>>> string? I mean, I know Objectify builds queries like:
This is actually one of my "crazy" idea mainly because we have an old system that I ported with AppEngine and it only knows JDBC and JPA queries, but I don't want to do JPA as it is very hard to maintain, I'd rather use Objectify.
On Saturday, November 3, 2012 11:41:56 PM UTC+8, Jeff Schnitzer wrote:
> You should have no trouble using JPA and Objectify in the same project as > long as you keep the entity classes in sync. Although, if you are going to > go through that trouble, why not just use JPA?
> The only major impedance mismatches will be polymoprhism, some edge cases > in @Embed collections (specifically null handling), and partial indexes > (which don't exist in JPA).
> Jeff
> On Fri, Nov 2, 2012 at 4:37 PM, Xybrek <xyb...@gmail.com <javascript:>>wrote:
>> While thinking of doing this feature, for me to move on with our project, >> is it possible that JPA and Objectify to work together, that is persisted >> Entities using Objectify be queried by JPA and vice versa?
>> On Saturday, November 3, 2012 1:41:41 AM UTC+8, Jeff Schnitzer wrote:
>>> There is not currently any plan. If you want to build some sort of >>> parser, we might consider including it... but this is a nontrivial feature.
>>> On Fri, Nov 2, 2012 at 12:56 PM, Xybrek <xyb...@gmail.com> wrote:
>>>> Is it possible to build a Query object with Objectify with a query >>>> string? I mean, I know Objectify builds queries like: