Hello, 2015-05-04 17:29 GMT+02:00 <[email protected]>:
> Hi Lukas, > > sorry, I forgot to send a code snippet. > No worries ;-) > In my case the optional type is not a good idea cause the ID which should > match to one object have to exist. > But I understand my mistake and I like the 'fetchOneInto' method. > I see. Yes, Optional would be wrong, then. Note that we also have a fetchExactlyOne() method on the roadmap (naming may vary): https://github.com/jOOQ/jOOQ/issues/3743 But that will also throw an exception in case no record was encountered... -- 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/d/optout.
