openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milosz Tylenda (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-736) Combine insert and select SQL together for generated Id strategy=GenerationType.IDENTITY
Date Sun, 31 May 2009 10:00:07 GMT

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

Milosz Tylenda resolved OPENJPA-736.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0

Change applied also to 1.3.x branch.

> Combine insert and select SQL together for generated Id strategy=GenerationType.IDENTITY

> -----------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-736
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-736
>             Project: OpenJPA
>          Issue Type: Improvement
>    Affects Versions: 1.3.0
>            Reporter: Fay Wang
>            Assignee: Milosz Tylenda
>             Fix For: 1.3.0, 2.0.0
>
>         Attachments: openjpa-736.patch, supportsGetGeneratedKeys.patch
>
>
> Currently if the strategy of the generated id is GenerationType.IDENTITY,  when an entity
object is created, openjpa will generate two SQL statements. The following is an example running
on DB2:
> (1) INSERT INTO EntityA (col1, col2, col3, version) VALUES (?, ?, ?, ?) 
> [params=(int) 1, (int) 1, (int) 1, (int) 1]
> (2) SELECT IDENTITY_VAL_LOCAL() FROM SYSIBM.SYSDUMMY1
> A performance improvement is to take advantage of the "select from final table" feature
in DB2 to combine the insert and select statement into a single SQL statement as shown below:
> SELECT id FROM FINAL TABLE (INSERT INTO EntityA (col1, col2, col3, version) VALUES (?,
?, ?, ?) )

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message