Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327065 - MaxDB: Allow creating temporary tables with PK columns only
Summary: MaxDB: Allow creating temporary tables with PK columns only
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Adrian Goerler CLA
QA Contact:
URL:
Whiteboard: maxdb
Keywords:
Depends on:
Blocks: 284657
  Show dependency tree
 
Reported: 2010-10-06 02:58 EDT by Adrian Goerler CLA
Modified: 2022-06-09 10:02 EDT (History)
4 users (show)

See Also:

Attachments
proposed patch (857 bytes, patch)
2010-10-06 03:36 EDT, Adrian Goerler CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian Goerler CLA 2010-10-06 02:58:03 EDT 
EclipseLink sometimes creates a temporary table to avoid a "self-modifying subquery". This temporary typed like an existing table. Sometimes, however, only the PK columns are needed. 

So far, MaxDB uses a 

CREATE TABLE <temp> LIKE <existing>

statement. However, this techinique does not allow to restrict to the PK columns only.
Comment 1 Adrian Goerler CLA 2010-10-06 03:36:26 EDT 
Created attachment 180297 [details]
proposed patch

Tested on MaxDB.
Checked in at 8320.
Comment 2 Adrian Goerler CLA 2010-10-06 04:29:34 EDT 
Fixes the issues with 

JUnitJPQLExamplesTestSuite 
.testDeleteExpression 
.testComplexDeleteExpression
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:02:43 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink