Hi Venkat, 2013/9/23 Venkat Sadasivam <[email protected]>
> Ran into a show stopper issue of not able to update primary key column > values. > This is a show stopper to you? Could you elaborate a little on what makes this an important missing feature? > I feel jOOQ should provide a way to update primary key value through > Record objects. > > http://www.jooq.org/javadoc/latest/org/jooq/UpdatableRecord.html#store() > > Can I have your thoughts on this? > Sure. Just as mentioned on the store() method, the rationale behind this is simple: 1. jOOQ assumes working on a normalised schema. Changing primary key values is usually not expected practice. 2. If the primary needs to be changed, then this is mostly due to scripting / batching behaviour, where regular SQL is better suited than CRUD. Now, the above is certainly debatable. There is room for changing such behaviour in a major release, or enhancing it in a minor release. But I'd really like to understand the use case behind changing primary key values, first. In some databases, this may result in table locks, which usually not desireable... 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.
