They exist, but not in the connection of the code generator, right?
Do they also exist in the INFORMATION_SCHEMA.TABLES dictionary view? Or how
else could the code generator discover them?


2014-01-29 Sha <[email protected]>

> Thank you.
> But in SQLServer DB , the temp tables exists though out connection. Until
> we delete them explicitly.
> Anyhow let me check what are all other ways available in JOOQ.
>
> ~Shyam
>
> On Wednesday, January 29, 2014 2:49:17 PM UTC+5:30, Lukas Eder wrote:
>>
>>
>>
>> 2014-01-29 Sha <[email protected]>
>>
>> Hi Lukas,
>>>   Does JOOQ code generator not have capability to convert temporary
>>> tables like normal tables ?
>>>
>>> As show in the attached file.
>>> I have create a temporary table in SQLServer DB.
>>> After i generate the files using code generator , I dont find the files
>>> related to Temporary tables.
>>>
>>> 1) Does the JOOQ has capability to handle temporary table as it has with
>>> normal tables?
>>>
>>
>> No. Again, because T-SQL temporary tables have no meaning outside of a
>> T-SQL context. You can keep trying this as many times as you want, but I've
>> been trying to tell you that you cannot use a T-SQL temporary table outside
>> of the very connection / session that has created it. This means that
>> they're not available to JDBC nor to jOOQ, specifically not to the code
>> generator. This is not a jOOQ problem, but a T-SQL limitation. T-SQL
>> temporary tables aren't as powerful as Oracle's.
>>
>> You'll find plenty of resources on the web, e.g.
>> http://stackoverflow.com/q/12595709/521799
>>
>  --
> 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.
>

-- 
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.

Reply via email to