| JPA Catalog Explorer and JPQL Query Builder [message #50731] |
Wed, 08 October 2008 07:27  |
Eclipse User |
|
|
|
Originally posted by: philippeweber57.yahoo.fr
Hi,
in the scope of my project I'm customizing the SQL Query Builder from
DTP to leverage select statement creation, I created a custom dtp
enablement project as input for the Query Builder and I intend to use
JPA inside the catalog provider. Getting far from simple Database/SQL...
I found that the work done on modelbase for SQL is really great, and I'm
wondering how it could serve (as basis or example) JPA and JPQL more
generally.
One idea would be to have a JPA Source Explorer similar to display JPA
catalogs provided by plug-ins, and a JPQL Editor with a QueryBuilder
with correct content assist read from JPA catalogs (bundled in plug-in).
I don't know if JPA could be used as the input of DTP defining a
enablement project, or if a fully new datatools.modelbase.jpql and
datatools.jpqltools would be needed.
Maybe the experts could light me up on these part.
In a short term, I'll anyway need to tweak the SQL Query Builder for my
needs, maybe up to the parser. But thinking generally, maybe a part of
all this could be reused.
Any comments are welcomed.
Regards,
Philippe
|
|
|
| Re: JPA Catalog Explorer and JPQL Query Builder [message #50926 is a reply to message #50731] |
Wed, 15 October 2008 20:39  |
| Eclipse User |
|
|
|
Can you describe how JPQL is similar or different from standard SQL?
Suggestions (and patches) on how to generalize the SQL Query Builder to
handle more SQL (or semi-SQL) dialects would be welcome.
Philippe Weber wrote:
> Hi,
>
> in the scope of my project I'm customizing the SQL Query Builder from
> DTP to leverage select statement creation, I created a custom dtp
> enablement project as input for the Query Builder and I intend to use
> JPA inside the catalog provider. Getting far from simple Database/SQL...
>
> I found that the work done on modelbase for SQL is really great, and I'm
> wondering how it could serve (as basis or example) JPA and JPQL more
> generally.
>
> One idea would be to have a JPA Source Explorer similar to display JPA
> catalogs provided by plug-ins, and a JPQL Editor with a QueryBuilder
> with correct content assist read from JPA catalogs (bundled in plug-in).
> I don't know if JPA could be used as the input of DTP defining a
> enablement project, or if a fully new datatools.modelbase.jpql and
> datatools.jpqltools would be needed.
> Maybe the experts could light me up on these part.
>
> In a short term, I'll anyway need to tweak the SQL Query Builder for my
> needs, maybe up to the parser. But thinking generally, maybe a part of
> all this could be reused.
>
> Any comments are welcomed.
>
> Regards,
> Philippe
|
|
|
| Re: JPA Catalog Explorer and JPQL Query Builder [message #50953 is a reply to message #50926] |
Thu, 16 October 2008 15:06 |
| Eclipse User |
|
|
|
Brian,
The main conceptual difference between JPQL and SQL is that JPQL queries
are defined against JPA entities (objects), as opposed to being directly
written against a database schema. When data needs to be stored or
retrieved from a relational database a JPA runtime will generally do this
on the back-end via SQL.
Take a look at this article for the basics on JPQL and how it relates to
SQL - http://www.oracle.com/technology/pub/articles/vasiliev-jpql. html
Neil
Brian Payton wrote:
> Can you describe how JPQL is similar or different from standard SQL?
> Suggestions (and patches) on how to generalize the SQL Query Builder to
> handle more SQL (or semi-SQL) dialects would be welcome.
> Philippe Weber wrote:
>> Hi,
>>
>> in the scope of my project I'm customizing the SQL Query Builder from
>> DTP to leverage select statement creation, I created a custom dtp
>> enablement project as input for the Query Builder and I intend to use
>> JPA inside the catalog provider. Getting far from simple Database/SQL...
>>
>> I found that the work done on modelbase for SQL is really great, and I'm
>> wondering how it could serve (as basis or example) JPA and JPQL more
>> generally.
>>
>> One idea would be to have a JPA Source Explorer similar to display JPA
>> catalogs provided by plug-ins, and a JPQL Editor with a QueryBuilder
>> with correct content assist read from JPA catalogs (bundled in plug-in).
>> I don't know if JPA could be used as the input of DTP defining a
>> enablement project, or if a fully new datatools.modelbase.jpql and
>> datatools.jpqltools would be needed.
>> Maybe the experts could light me up on these part.
>>
>> In a short term, I'll anyway need to tweak the SQL Query Builder for my
>> needs, maybe up to the parser. But thinking generally, maybe a part of
>> all this could be reused.
>>
>> Any comments are welcomed.
>>
>> Regards,
>> Philippe
|
|
|
| Re: JPA Catalog Explorer and JPQL Query Builder [message #593552 is a reply to message #50731] |
Wed, 15 October 2008 20:39 |
| Eclipse User |
|
|
|
Can you describe how JPQL is similar or different from standard SQL?
Suggestions (and patches) on how to generalize the SQL Query Builder to
handle more SQL (or semi-SQL) dialects would be welcome.
Philippe Weber wrote:
> Hi,
>
> in the scope of my project I'm customizing the SQL Query Builder from
> DTP to leverage select statement creation, I created a custom dtp
> enablement project as input for the Query Builder and I intend to use
> JPA inside the catalog provider. Getting far from simple Database/SQL...
>
> I found that the work done on modelbase for SQL is really great, and I'm
> wondering how it could serve (as basis or example) JPA and JPQL more
> generally.
>
> One idea would be to have a JPA Source Explorer similar to display JPA
> catalogs provided by plug-ins, and a JPQL Editor with a QueryBuilder
> with correct content assist read from JPA catalogs (bundled in plug-in).
> I don't know if JPA could be used as the input of DTP defining a
> enablement project, or if a fully new datatools.modelbase.jpql and
> datatools.jpqltools would be needed.
> Maybe the experts could light me up on these part.
>
> In a short term, I'll anyway need to tweak the SQL Query Builder for my
> needs, maybe up to the parser. But thinking generally, maybe a part of
> all this could be reused.
>
> Any comments are welcomed.
>
> Regards,
> Philippe
|
|
|
| Re: JPA Catalog Explorer and JPQL Query Builder [message #593562 is a reply to message #50926] |
Thu, 16 October 2008 15:06 |
| Eclipse User |
|
|
|
Brian,
The main conceptual difference between JPQL and SQL is that JPQL queries
are defined against JPA entities (objects), as opposed to being directly
written against a database schema. When data needs to be stored or
retrieved from a relational database a JPA runtime will generally do this
on the back-end via SQL.
Take a look at this article for the basics on JPQL and how it relates to
SQL - http://www.oracle.com/technology/pub/articles/vasiliev-jpql. html
Neil
Brian Payton wrote:
> Can you describe how JPQL is similar or different from standard SQL?
> Suggestions (and patches) on how to generalize the SQL Query Builder to
> handle more SQL (or semi-SQL) dialects would be welcome.
> Philippe Weber wrote:
>> Hi,
>>
>> in the scope of my project I'm customizing the SQL Query Builder from
>> DTP to leverage select statement creation, I created a custom dtp
>> enablement project as input for the Query Builder and I intend to use
>> JPA inside the catalog provider. Getting far from simple Database/SQL...
>>
>> I found that the work done on modelbase for SQL is really great, and I'm
>> wondering how it could serve (as basis or example) JPA and JPQL more
>> generally.
>>
>> One idea would be to have a JPA Source Explorer similar to display JPA
>> catalogs provided by plug-ins, and a JPQL Editor with a QueryBuilder
>> with correct content assist read from JPA catalogs (bundled in plug-in).
>> I don't know if JPA could be used as the input of DTP defining a
>> enablement project, or if a fully new datatools.modelbase.jpql and
>> datatools.jpqltools would be needed.
>> Maybe the experts could light me up on these part.
>>
>> In a short term, I'll anyway need to tweak the SQL Query Builder for my
>> needs, maybe up to the parser. But thinking generally, maybe a part of
>> all this could be reused.
>>
>> Any comments are welcomed.
>>
>> Regards,
>> Philippe
|
|
|
Powered by
FUDForum. Page generated in 0.05029 seconds
Home