On Sat, Mar 30, 2024 at 6:21 AM wrote:
> Do you have any thoughts around when this enhancement might come out in a
> release?
Probably in the next couple of weeks pending feedback.
Paul.
: Re: SQL enhancement request (GROOVY-11342)
That would be eachRowWithIndex, which would imho be nice to have here, as well
as for collect (i.e. collectWithIndex)... ;-)
Cheers,
mg
On 29/03/2024 19:17, steve.etchel...@gmail.com
<mailto:steve.etchel...@gmail.com> wrote:
Basically ther
That would be eachRowWithIndex, which would imho be nice to have here,
as well as for collect (i.e. collectWithIndex)... ;-)
Cheers,
mg
On 29/03/2024 19:17, steve.etchel...@gmail.com wrote:
Basically there's no way to get eachRow() to provide a counter...
Message-
From: steve.etchel...@gmail.com
Sent: Friday, March 29, 2024 1:17 PM
To: users@groovy.apache.org
Subject: RE: SQL enhancement request (GROOVY-11342)
Thanks Paul! I thought that eachrow iteration issue had something to do with
eachRow() possibly not returning a List but when I saw it
${row[colid]}' ...
}
rowid++
}
Thanks,
Steve
-----Original Message-
From: Paul King
Sent: Thursday, March 28, 2024 9:05 PM
To: users@groovy.apache.org
Subject: Re: SQL enhancement request (GROOVY-11342)
Well spotted for eachRow. You can fix that with:
rom earlier Oracle/Teradata/SQLServer/MySQL
> environments and have basically found Denodo to be a plug-n-play drop-in
> replacement for their earlier databases.
>
> I was happy to see that apparently I understood how to handle the two closure
> calls correctly! And you didn't
to) throw up when you saw my metaClosure
definition with its three parallel lists! If there's a better/groovier way to
accomplish what I'm doing in that closure I'm open to learning. :)
Apologies for the lengthy email and thanks again,
Steve
-Original Message-
Fro
And any educational feedback you might have would be greatly appreciated!
> After all I'm sure you have plenty of free time to donate! :D
>
> So the approach you mentioned of adding a new variant to execute() that adds
> a metaClosure would be perfect, though I've reall
though I've really gotten comfortable with the
rows() method - not sure how it scales when resultSets go to billions of rows
though... I expect execute() would perform like a streaming interface and not
have any problems at scale.
Thanks for all your help, couldn't have made it this f
erience for me
though.
Thanks,
Steve
-Original Message-
From: Paul King
Sent: Monday, March 25, 2024 8:03 PM
To: users@groovy.apache.org
Subject: Re: SQL enhancement request
Adding a metaClosure to execute seems the easiest change. I created
GROOVY-11342 to track here:
https://issues.ap
s" (eachRow,
> rows, and execute) so that they all have a variant with a metaClosure and/or
> a two-parameter processResults closure.
>
> Thanks,
> Steve
>
> -Original Message-
> From: Jörg Prante
> Sent: Friday, March 22, 2024 12:03 PM
> To:
Sent: Friday, March 22, 2024 12:03 PM
To: users@groovy.apache.org
Subject: Re: SQL enhancement request
Hi Steve,
just use this Sql.execute method
https://docs.groovy-lang.org/latest/html/api/groovy/sql/Sql.html#execute(java.lang.String,groovy.lang.Closure)
to send arbitrary statements and decid
Hi Steve,
just use this Sql.execute method
https://docs.groovy-lang.org/latest/html/api/groovy/sql/Sql.html#execute(java.lang.String,groovy.lang.Closure)
to send arbitrary statements and decide by the isResultSet flag in the
closure whether you have to obtain a result set from a select query, or
Greetings,
As sort of a side note, you may want to take a look at my Kiss open-source,
full-stack web development framework. It includes a super easy to use SQL
API that is accessible from Groovy. This API is currently being used in
several large-scale, enterprise, production systems. kissweb.o
Groovy team,
It is my understanding (which can always be improved!) that Groovy SQL supports
about 3 “families” of interaction methods – execute() and its variants, rows()
and eachRow() for submitting SQL statements and processing any results
generated.
Each of them has a variety of sign
15 matches
Mail list logo