[jira] [Updated] (GORA-86) Support JOOQ API within gora-sql module

2019-05-02 Thread Kevin Ratnasekera (JIRA)


 [ 
https://issues.apache.org/jira/browse/GORA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Ratnasekera updated GORA-86:
--
Fix Version/s: (was: 0.9)
   1.0

> 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
(v7.6.3#76005)


[jira] [Updated] (GORA-86) Support JOOQ API within gora-sql module

2016-03-24 Thread Lewis John McGibbney (JIRA)

 [ 
https://issues.apache.org/jira/browse/GORA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated GORA-86:
-
Labels: gsoc2014 gsoc2016 mentor  (was: gsoc2014 mentor)

> 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
>  Labels: gsoc2014, gsoc2016, mentor
> Fix For: 0.8
>
> 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
(v6.3.4#6332)


[jira] [Updated] (GORA-86) Support JOOQ API within gora-sql module

2014-03-25 Thread Apostolos Giannakidis (JIRA)

 [ 
https://issues.apache.org/jira/browse/GORA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apostolos Giannakidis updated GORA-86:
--

Labels: gsoc2014 mentor  (was: gsoc2014)

 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
  Labels: gsoc2014, mentor
 Fix For: 0.4

 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
(v6.2#6252)


[jira] [Updated] (GORA-86) Support JOOQ API within gora-sql module

2014-03-24 Thread Fathima Hasna (JIRA)

 [ 
https://issues.apache.org/jira/browse/GORA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Fathima Hasna updated GORA-86:
--

Attachment: gsoc_proposal.docx

I have attached my GSOC proposal here. Please review it and provide me your 
suggestions.

 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
  Labels: gsoc2014
 Fix For: 0.4

 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
(v6.2#6252)


[jira] [Updated] (GORA-86) Support JOOQ API within gora-sql module

2014-02-05 Thread Lewis John McGibbney (JIRA)

 [ 
https://issues.apache.org/jira/browse/GORA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lewis John McGibbney updated GORA-86:
-

Labels: gsoc2014  (was: )

 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
  Labels: gsoc2014
 Fix For: 0.4


 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
(v6.1.5#6160)