I too vote for option 3.
On Thu, Jun 14, 2018 at 12:49 PM, Cédric Champeau wrote:
> I vote for option 3
>
> Le jeu. 14 juin 2018 à 18:46, Russel Winder a
> écrit :
>
>> On Wed, 2018-06-13 at 14:53 -0400, Keith Suderman wrote:
>> > >
>> […]
>> > How about an option #4. If you are planning to do
honestly the poll looks like a attempt to get a list of email address for
security/audit consulting :)
On Sat, May 12, 2018 at 11:43 AM, Russel Winder
wrote:
> On Sat, 2018-05-12 at 10:51 -0400, Keegan Witt wrote:
> > It's unfortunate it won't let you choose multiple primary application
> > lan
hibernate 5 supports java.time via hibernate-java8.jar
more info at https://www.thoughts-on-java.org/hibernate-5-date-and-time/
JPA doesn't yet till 2.2
On Thu, Jun 8, 2017 at 11:21 PM, Tankerbay wrote:
> Is there still a legacy issue in that many ORMs (including the version of
> Grails I'm us
wow, the Mandarin one is pretty good :)
On Wed, Mar 29, 2017 at 6:04 PM, Guillaume Laforge
wrote:
> Arabic, Mandarin and Emoji are pretty fun! Nicely done! :-)
>
> Guillaume
>
>
> On Fri, Mar 24, 2017 at 5:20 PM, frenchy48 wrote:
>
>> I implemented a funny experiment on top of Groovy: using my
as I recall, there are also rules about jigsaw not allowing same package
path from multiple modules. It's not till java 9, but that maybe a concern.
On Mon, Mar 27, 2017 at 3:28 PM, Guillaume Laforge
wrote:
> Just an added note on the topic of potential package name changes.
>
> In the past, we'
d to use jOOQ.
> Le 23 juin 2016 06:58, "Wilson MacGyver" a écrit :
>
>> Ouch I will continue to embrace dynamic then :)
>>
>> On Wed, Jun 22, 2016 at 1:56 PM Guillaume Laforge
>> wrote:
>>
>>> Perhaps a custom type checker extension could b
I think what Jochen means is, Indy requires jdk 7. Once 9 comes out, it
will be safe to drop Jdk 6 support.
Thus no need for non Indy version
On Thu, Jun 23, 2016 at 9:50 AM Winnebeck, Jason <
jason.winneb...@windstream.com> wrote:
> I am curious, what does JDK 9 change to affect indy?
>
> As fo
t;
>> You could use the map access syntax i.e. foo['id'] instead and
>> cast/coerce the result to the appropriate type.
>>
>> On Wed, Jun 22, 2016 at 1:37 PM Wilson MacGyver
>> wrote:
>>
>>> Hi,
>>>
>>> If I want
Hi,
If I want to use compileStatic with groovy.sql, how would I do that?
the problem as far as I can tell is
sql.eachRow("select id, from whatever") { foo ->
...
foo.id
}
returns data that is known at runtime
but at compile time. there is no way to know that the SQL statement returns
a
