Hi Kevin,

Did casting yield any results? Could you track down the problem to
something specific?

Thanks,
Lukas

On Tue, May 4, 2021 at 1:34 PM [email protected] <[email protected]>
wrote:

> Thank you for the response,
> Postgers Version 10.16
> org.postgresql.Driver (version 42.2)
>
> Must of cut and pasted in between tries. I tried
> .fetchOne()
> .fetchOneInto(GetTransactionRecordRecord.class)
> .fetch()
> .fetchInto(GetTransactionRecordRecord.class)
>
> All with the same result.
>
> I will try the explicit casting and see if that makes any difference and
> also see about setting up a MVCE as well. Hopefully that will bring to
> light the problem.
>
> Thanks,
> Kevin
> On Tuesday, May 4, 2021 at 2:20:05 AM UTC-4 [email protected] wrote:
>
>> Kevin, the missing precision on the timestamp precision in generated code
>> might be due to https://github.com/jOOQ/jOOQ/issues/11191, but wouldn't
>> affect the query in the way you're seeing.
>>
>> You could indeed attempt to explicitly cast your arguments (e.g.
>> inline("").cast(VARCHAR)), but I don't see why you should have to. When
>> you're inlining the arguments, then PostgreSQL should be able to infer the
>> types (I can't reproduce your problem on my machine, with PostgreSQL 13 -
>> what version are you using of PostgreSQL and of the jdbc driver?).
>>
>> I wonder if the jOOQ code you've shown is really the code you've
>> executed. Your stack trace shows fetchInto(), but you're showing a call to
>> fetchOne() - might not be relevant.
>>
>> Can you help reproduce this? We have a template to create MCVE's
>> (minimal, complete, verifiable examples) here:
>> https://github.com/jOOQ/jOOQ-mcve but any other way would be useful too.
>> I'd be looking out for anything specific to your setup, including your
>> Settings, JDBC connection parameters, software versions, etc.
>>
>> Thanks,
>> Lukas
>>
>> On Tue, May 4, 2021 at 4:51 AM Rob Sargent <[email protected]> wrote:
>>
>>> Far as I can tell you only show three of the columns for the function
>>> def (schema, name, return type).
>>>
>>>
>>> khoj.get_transaction_record(unknown, unknown, unknown, unknown) does not
>>> exist
>>>
>>> But the parser doesn’t know the data type of each arg you’re passing
>>> in.  Have you tried wrapping those in “cast”, especially the date.
>>>
>>> This seems a very cumbersome way of useing jOOQ.  Have you not generated
>>> classes, including for the functions?
>>>
>>>
>>>
>>>
>>> On May 3, 2021, at 8:32 PM, [email protected] <[email protected]>
>>> wrote:
>>>
>>> khoj   | get_transaction_record | TABLE(uuid uuid, date_of_creation
>>> timestamp without time zone, date_of_expiration timestamp without time
>>> zone, user_name character varying, break_point bigint)|
>>>
>>>
>>> --
>>> 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].
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jooq-user/9F223085-88D8-45CA-871B-6112FD127C2B%40gmail.com
>>> <https://groups.google.com/d/msgid/jooq-user/9F223085-88D8-45CA-871B-6112FD127C2B%40gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jooq-user/ef6555a5-1b6e-4b9a-bbe8-6e3091f7893en%40googlegroups.com
> <https://groups.google.com/d/msgid/jooq-user/ef6555a5-1b6e-4b9a-bbe8-6e3091f7893en%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jooq-user/CAB4ELO690dAFWpcZ1Ln914tenrnoVoJtbSDO3PD63bu4_GVAAA%40mail.gmail.com.

Reply via email to