> Actually, I didn't expect a response that soon! By coincidence, I had been studying the use of tuples in other languages like Scala and C# for some time now. Specifically, the potential addition of tuple / record types has been mentioned by Brian Goetz on the lambda-dev mailing list, something which I have blogged about, here: http://blog.jooq.org/2012/06/01/array-list-set-map-tuple-record-literals-in-java/
So this topic has been on my mind for a while. Your support request, as well as Ben's here, just lead to me deciding that the time is now ripe: https://groups.google.com/d/topic/jooq-user/TAaq63ciO7M/discussion A nice coincidence, so to say > So, what can I say? I expected the same solution for tuples you suggested > and implemented. I think it's great! Thanks for the feedback. > Btw, my use case was selecting by composite key. May be I should have tried > UDTs instead? That is a good point. I was thinking about adding improved multi-column primary key / foreign key support to jOOQ: https://github.com/jOOQ/jOOQ/issues/1690 I was thinking about adding a new type for this, but using the new Tuple types seems even better. As such, tuples could become a more integral part of the jOOQ API, replacing some occurrences of Field<?>[] method arguments... About UDTs: Personally, I have no experience in using UDTs as keys in Oracle. I'm not sure how they behave in terms of indexing and constraint violation performance. It might be a viable option, though. Cheers Lukas
