Re: Using DSL api to construct sql queries

Hi, A little late here but form a quick look it should be OK. The jOOQ runtime (which I assume is the bit you want to use) is Apache licensed and what it depends is compatible. You could not bundle the jOOQ-meta-extensions in source or binary release as it depends on Category B license (MPL)

Re: Using DSL api to construct sql queries

Hi, Does anyone has inputs on licensing part? I will start a new mail thread to discuss that issue separately. -Priyanka On Fri, Jul 22, 2016 at 11:58 PM, Pradeep A. Dalvi wrote: > +1 From what I read, this change is completely backword compatible. > > --prad > > On Thu, Jul

Re: Using DSL api to construct sql queries

+1 From what I read, this change is completely backword compatible. --prad On Thu, Jul 21, 2016 at 11:13 PM, Chinmay Kolhatkar wrote: > Yes there is no clash with calcite integration. Calcite is a query planner > converts SQL to a relational algebra... This is

Re: Using DSL api to construct sql queries

Yes there is no clash with calcite integration. Calcite is a query planner converts SQL to a relational algebra... This is different. On Fri, Jul 22, 2016 at 11:03 AM, Priyanka Gugale wrote: > I don't know much about Calcite, but reading abstract, calcite seems to be > for

Re: Using DSL api to construct sql queries

I don't know much about Calcite, but reading abstract, calcite seems to be for different purpose. What I want to achieve here is some library which will let me construct sql query without worrying about different DB platforms. The library will take care of converting query to the DB specific

Re: Using DSL api to construct sql queries

But is it a duplication of integration with Calcite? On Thu, Jul 21, 2016 at 9:26 AM, Timothy Farkas < timothytiborfar...@gmail.com> wrote: > I see, cool :) > > On Thu, Jul 21, 2016 at 9:21 AM, Priyanka Gugale > wrote: > > > Hi Tim, > > > > We are not creating our own DSL,

Re: Using DSL api to construct sql queries

I see, cool :) On Thu, Jul 21, 2016 at 9:21 AM, Priyanka Gugale wrote: > Hi Tim, > > We are not creating our own DSL, the jooq is just another query > parser/builder like JsqlParser. I am trying to use one of these query DSL > libraries to replace the existing code in

Re: Using DSL api to construct sql queries

Hi Tim, We are not creating our own DSL, the jooq is just another query parser/builder like JsqlParser. I am trying to use one of these query DSL libraries to replace the existing code in operator which is written to construct the queries. -Priyanka On Thu, Jul 21, 2016 at 9:42 PM, Timothy

Re: Using DSL api to construct sql queries

I don't know the exact context here so please forgive me if I'm mistaken. I don't think creating our own DSL is the way to go. Creating a generic DSL is hard. We should support setting the flavor of SQL being used as a property and then allow standard sql to be specified. There are already mature

Re: Using DSL api to construct sql queries

Looking closely at licensing, it says it *depends but doesn't bundle* those non ASL license dependencies. As per my understanding those will be included only if we explicitly include them using our application pom. Right away we are not using any of those features which depend of such third party

Re: Using DSL api to construct sql queries

It is a good idea to get rid of vendor specific implementation differences for SQL. However, the licensing does not seem to be straightforward. Please check: http://www.jooq.org/legal/licensing. Can this be used as a dependency in Apex? ~ Bhupesh On Wed, Jul 20, 2016 at 3:06 AM, Priyanka Gugale