+1 It happened to me so many times that I always refactor my deletes into separate methods returning ints, so that I get compilation errors in case I forget to call execute().
Le dimanche 26 octobre 2014 09:49:37 UTC+1, Lukas Eder a écrit : > > Hello, > > Thanks for reaching out to us. Yes, we're aware of this and we'll try to > improve that pretty soon. There is already a pending feature request for > adding .fetch() and .execute() methods everywhere: > https://github.com/jOOQ/jOOQ/issues/3170 > > Cheers > Lukas > > 2014-10-25 1:33 GMT+02:00 <[email protected] <javascript:>>: > >> Hi >> >> In >> http://www.jooq.org/doc/3.1/manual/sql-building/sql-statements/delete-statement/ >> >> I found >> >> create.delete(AUTHOR) >> .where(AUTHOR.ID.equal(100)); >> >> I struggled quite a bit before I added execute() at the end of this >> statement (I found a comment in the delete()-method). Then it worked fine. >> >> kind regards >> >> Morten S >> >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
