gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashanka Balakuntala Srinivasa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-86) Support JOOQ API within gora-sql module
Date Wed, 10 Jul 2019 07:44:00 GMT

    [ https://issues.apache.org/jira/browse/GORA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881801#comment-16881801

Shashanka Balakuntala Srinivasa commented on GORA-86:


I have started the implementation of this module using JOOQ api. The current implementation
passed all the test cases which was provided in gora-0.8 module but requires some improvements.
And to add the implementation also worked for MySQL, HSQL and Vitess DB(A database clustering
system for horizontal scaling of MySQL). I'm working on implementing the where clause of the
module and want to know if I'm headed in the right direction, is there anyone who I can contact
regarding this.

> Support JOOQ API within gora-sql module 
> ----------------------------------------
>                 Key: GORA-86
>                 URL: https://issues.apache.org/jira/browse/GORA-86
>             Project: Apache Gora
>          Issue Type: Improvement
>          Components: gora-sql
>    Affects Versions: 0.2
>            Reporter: Lewis John McGibbney
>            Priority: Major
>              Labels: gsoc2014, gsoc2016, mentor
>             Fix For: 1.0
>         Attachments: gsoc_proposal.docx
> We've discussed this recently and Lukas Eder has been helpful enough to provide an his
opinion, which acts as an overview from a different perspective, on whether JOOQ is appropriate
for Gora. 
> This issue should act as a separate but linked issue to GORA-74, and we should discuss
what happens to the SQL type code that we maintain within Gora. As this module is not being
utilised very much just now there is really no overwhelming argument yet to adopt JOOQ, however
hopefully we can iron this out within the correspondence.  

This message was sent by Atlassian JIRA

View raw message