Hi Shyam, I am very sorry to hear that you have found such great disappointment in this particular missing feature. Rest assured that we are carefully planning our roadmap according to the needs of our customers, who can influence the roadmap according to their specific needs.
In the case of the vendor-specific UPDATE .. FROM clause, we have found this SQL extension to be a lower priority with our existing customers thus far. This does not mean that we cannot change this priority in the near future. You, yourself, have offered very challenging requirements on this user group so far, and we've found this experience to be very interesting. A customer like yourself is a great opportunity to help make jOOQ even better than today, as we're constantly learning from requirements as yours. I hope you will continue to like jOOQ for its existing good parts, with patience towards the missing SQL features, which we will certainly support sooner or later. Best Regards, Lukas 2014-02-03 Sha <[email protected]>: > Thank you for your quick reply. > Lukas, > I think JOOQ does not handle many complex scenarios like this. I > personally feel that JOOQ should make enable to handle complex scenarios. > Otherwise it is difficult to win the hearts of developer community to look > as an option for some critical application development. > Its really disappointing. > > ~Shyam > > > On Friday, January 31, 2014 11:22:52 PM UTC+5:30, Lukas Eder wrote: > >> Hi Shyam, >> >> Please consider the previous question you've asked on that subject: >> https://groups.google.com/forum/#!searchin/jooq-user/ >> update$20from$20shyam/jooq-user/T7MC5HXeDjQ/apvEI9OZAcEJ >> >> Cheers >> Lukas >> >> >> 2014-01-31 Sha <[email protected]>: >> >>> Hi Lukas, >>> >>> I have following scenario where i am getting error. >>> >>> *The original SQL code snippet * >>> >>> update #NODE_TEMP set already_exists = 1 >>> * from #NODE_TEMP nt* >>> join book_plane bp on nt.plane_id = bp.plane_id >>> join book_detail bd >>> on nt.hc1_item_id = bd.hc1_leaf_id >>> >>> *My written JOOQ equalent is * >>> >>> Table nt= NODE_TEMP.as("nt"); >>> ctx.update(nt).set(nt.field("already_exists"), 1) >>> *.from(nt) //Error* >>> .join(bp) >>> .on( bp.PLANE_ID.eq(nt.field("PLANE_ID")) ) >>> .join(bd) >>> .on( (nt.field("hc1_item_id").eq(bd.HC1_LEAF_ID).and( nt.field( >>> "HC3_ITEM_ID").eq(bd.HC3_LEAF_ID)))) >>> >>> *Error* >>> The method from(Table) is undefined for the type UpdateSetMoreStep >>> >>> >>> How to write the equalent JOOQ code for the above shown SQL piece of >>> code. >>> i.e how to use joins in update statement of JOOQ. >>> >>> What is the way out ? >>> >>> Thank you. >>> ~Shyam >>> >>> -- >>> 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. >>> >> >> -- > 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. > -- 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.
