2014-02-28 19:02 GMT+01:00 Florian Gutmann <[email protected]>: > Hi Lukas! > > When using DSL.row with anything different then Field parameters, > compilation fails with an "ambiguous reference to overloaded definition" > error. > For example this code fails: > > row(1, 2) > > The reason seems to be that the scala compiler can't find out which of the > row methods is most specific. > > > http://stackoverflow.com/questions/3313929/how-do-i-disambiguate-in-scala-between-methods-with-vararg-and-without > > http://stackoverflow.com/questions/2159248/spurious-ambiguous-reference-error-in-scala-2-7-7-compiler-interpreter/2172619 > https://issues.scala-lang.org/browse/SI-2991 >
Thanks for the links. I have created an issue for this. Will investigate more later on: https://github.com/jOOQ/jOOQ/issues/3087 But I remember that some implicit Scala conversions used for improved Java/Scala interoperability can lead to such issues. Sorry, saying ResultQuery fetchInto doesn't work with scala classes was too > generic. > It doesn't work with case classes, which was the paradigm I wanted to use. > Hmm, what do case classes look like in byte code? Is there any constructor that jOOQ could call? How does it fail, do you get compilation errors, or an exception? I've also created an issue to track this: https://github.com/jOOQ/jOOQ/issues/3088 Cheers Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
