Hi J, I'm currently on vacation, and I do not have a substitute yet, at jOOQ to handle these requests... :)
If this can wait for another 2 weeks, I'll look into this more in depth later. In the mean time, you can try these things: - Change that CLOB column to a different type - Patch code generation logic to generate Field<String> for the affected columns - Check out the test project from subversion and see how the Clob and Blob integration tests work. As far as I can tell now, I intended not to fully support Clob and Blob types, but to map them to String and byte[]. Could be, that this isn't done correctly for the H2 code generation support... Cheers Lukas 2011/1/19 JMoger <[email protected]> > Granted I haven't spent a ton of time looking into this.... but I > haven't figured out how to use addValue with a CLOB. > > More specifically I want to be able to do the following: > > UpdateQuery<ProjectTableRecord> u = > create.updateQuery(ProjectTable.PROJECT_TABLE); > u.addValue(ProjectTable.DESCRIPTION, "I updated the description"); > u.addCompareCondition(ProjectTable.ID, id); > u.execute(); > > where DESCRIPTION is a CLOB. > > Background.... > I currently deploy on MySQL but do most development on H2. > In MySQL DESCRIPTION is a TEXT column and in H2 DESCRIPTION is a CLOB > column. > > The MySQL mapping generated by jOOQ accepts a String value for the > TEXT type. > The H2 mapping expects a CLOB value. > > I thought I RTFM, but perhaps I missed something. :) > > -J
