Issue Details (XML | Word | Printable)

Key: NUCRDBMS-381
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Andy Jefferson
Reporter: Andy Jefferson
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
DataNucleus Store RDBMS

SQL Table namers need to work with multiple levels of nested subqueries to create unique namings

Created: 29/Apr/10 08:59 AM   Updated: 24/May/10 03:43 PM   Resolved: 29/Apr/10 09:01 AM
Component/s: Queries
Affects Version/s: 2.0.0.release, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.1.0.m1, 2.1.0.m2
Fix Version/s: 2.1.0.m3


 Description  « Hide
In the current "alpha" table namer if the query has a parent then the table is named something like A0_SUB, B0_SUB. But this is also currently applied when the subquery parent is also a subquery. We really ought to use something like
A0_SUB, A0_SUB_SUB, etc

Andy Jefferson added a comment - 29/Apr/10 09:01 AM
SVN trunk handles this down to 3 levels now

Andy Jefferson made changes - 29/Apr/10 09:01 AM
Field Original Value New Value
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Andy Jefferson made changes - 24/May/10 03:43 PM
Status Resolved [ 5 ] Closed [ 6 ]