2016-11-18 11:52 GMT+01:00 Excrulon <[email protected]>: > Giving up for the night, but want to leave this here to make sure I'm > thinking about this whole thing correctly. > > I was under the impression that a converter is for when you come across a > certain type of column data type and you want to change it to a java object. > Yes.
> Example... a table in my postgres db has columns of type timestamp. So I > would declare timestamp in the types tag. > Yes indeed. > This makes it so whenever I run a jooq query and one of the columns is of > type timestamp, it will automatically trigger the converter class I have > defined for that type and run the proper overridden method that tells how > to convert it to my target result, ZonedDateTime. > Exactly. > You're saying it should be bigint over timestamp though... so am I > completely wrong on all of this? > No, I was confused by your code, which is why I brought up BIGINT. But certainly, there's something wrong somewhere because your converter uses java.lang.Long, rather than java.sql.Timestamp as the binding for the <T> type variable. Perhaps we don't have all the information to help you just yet? -- 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.
