Hey Lukas,
I can't confirm it - because I dont even know how to check if the class was
loaded.
Something like this - works - but will throw an exception once it is
returned to my trigger - is the converter registered now?
I tried skipping the first access to the trigger - this showed no change.
DSL.using(injector.getInstance(Configuration.class))
> .update(Tables.UPLOAD)
> .set(Tables.UPLOAD.INPROGRESS, false)
> .set(Tables.UPLOAD.FAILED, false)
> .set(Tables.UPLOAD.DATE_OF_START, (GregorianCalendar) null)
> .set(Tables.UPLOAD.DATE_OF_RELEASE, new GregorianCalendar())
> .execute();
>
For me it looks like fetchOne().into() or (fetchOneInto()) call a default
mapper and not the corresponding record mapper.
For example:
I tried following too - I assumed that I might have to convert the custom
record to a specific one:
final UploadRecord u =
> result.fetchOneInto(UploadRecord.class);
> final Upload record = u.into(Upload.class);
>
This fails at the exact same first conversion - so at least I can say that
not even the conversion to a specific UploadRecord works.
An alternative could be a different way of fetching the results in the
trigger:
Currently it uses final ResultSet oldRow, final ResultSet newRow
(java.sql.ResultSet) and with help of jooq lazyFetches the records.
- There is no other way than lazy fetching because the trigger would stuck
at a point where jooq would endlessly fetch rows. This is a strange
behavior by H2 and the reason for a little workaround (firstId, lastId
comparision to get the point of time all records have been processed).
Regards,
Dennis
--
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.
