Hi Simone, Result<R> implements List<R> and Record has setValue() methods, so you can do anything you want with such results. E.g.
result.get(0).setValue(TABLE.SEX, "Femmine") Beware that 'sex' field is VARCHAR(1) so I think there will not > be enough room to store 'Femmine' or 'Maschi' > jOOQ's in-memory model of Result doesn't care about the precision (although, this makes me think whether it should...). So as long as this stays in Java memory, you'll be on the safe side for now. However, I think you might be interested in "live data sets" that keep open cursors and store changes to the database. Is that so? In that case, the changes currently aren't stored back to the database. > Another situation is where I have one Result with three columns and I want > to merge two of them in one new calculated column. > Is there a way for such programmatic manipulation? > Why not use SQL for that? :-) Otherwise, we have implemented #3139 to create new ad-hoc in-memory Result objects based on your own set of fields: https://github.com/jOOQ/jOOQ/issues/3139 This is particularly useful when creating Mock results as documented here: http://www.jooq.org/doc/latest/manual/tools/jdbc-mocking Does this help? Thanks, 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/d/optout.
