You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Oscar Bonilla (JIRA)" <ji...@apache.org> on 2011/03/17 03:41:29 UTC

[jira] Updated: (DERBY-5138) Why can not create session indexes, session unique indexes and identity columns in temporary session tables

     [ https://issues.apache.org/jira/browse/DERBY-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oscar Bonilla updated DERBY-5138:
---------------------------------

    Attachment: DB2 script.txt

Example of DB2 behavoir

> Why can not create session indexes, session unique indexes and identity columns in temporary session tables
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5138
>                 URL: https://issues.apache.org/jira/browse/DERBY-5138
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.7.1.1
>         Environment: windows, linux
>            Reporter: Oscar Bonilla
>              Labels: features
>         Attachments: DB2 script.txt
>
>
> I am a senior programmer in sybase (transact sql) and Oracle. I had to convert a lot of programs to work in DB2. There are many processes that require a lot of rows in temporary tables that needs join together, and they expends much time to execute without indexes. I have to transform the logic to do that with permanent tables with indexes those I have to drop after the process. Now, DB2 can do "create unique index SESSION.xx_I01 on SESSION xx" and this resolve my problem with the efficienty of the processes. In another hand, I do not have any problem to use "GENERATED ALWAYS AS IDENTITY" in a temporary session table in DB2.  With this 2 issues it is imposible to migrate all the systems to work with Derby. Thank.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira