Issue Details (XML | Word | Printable)

Key: NUCRDBMS-586
Type: New Feature New Feature
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

Nondurable identity

Created: 20/Aug/05 08:53 PM   Updated: 14/May/12 07:45 PM   Resolved: 09/Apr/12 02:33 PM
Component/s: ORM
Affects Version/s: None
Fix Version/s: 3.1.0.m3


DataNucleus Admin added a comment - 20/Aug/05 08:53 PM
Support nondurable identity so that people who have tables that have no primary key can map a class to the table

Andy Jefferson made changes - 21/Aug/05 01:40 PM
Field Original Value New Value
Environment
Fix Version/s 1.2.0 [ 10021 ]
Fix Version/s 1.1.0 [ 10020 ]
Description
Reporter Andy Jefferson [ andy ]
Andy Jefferson made changes - 06/Sep/06 09:59 AM
Fix Version/s 1.2.0 [ 10021 ]
Andy Jefferson added a comment - 05/Dec/06 03:43 PM
Sample nondurable testcase

Andy Jefferson made changes - 05/Dec/06 03:43 PM
Attachment testcase.zip [ 10402 ]
Andy Jefferson made changes - 21/Apr/07 09:31 AM
Assignee Andy Jefferson [ andy ]
Andy Jefferson added a comment - 21/Apr/07 01:04 PM
The basic persistence capabilities are in CVS :-
1. When a class is marked as nondurable and using an RDBMS it will have a table without PK
2. Insert of object inserts all fields
3. Query/Extent retrieval extracts the objects and assigns SCOID to each object.
4. Relevant checks on use of pm.getObjectById are present

What isn't supported
1. Ability to update a single record and have only that record updated in the datastore (even when there are multiple records with these field values). This implies maybe having an "id" value added to the datastore object so that we can identify the one to update (or alternatively to generate SQL that will only update the first record with those param values), but by adding any column (like datastore id) we would be imposing on the user the need for an additional column.
2. Ability to use deletePersistent and only delete one record in the datastore. Currently deletePersistent will fail since the DeleteRequest will try to generate a statement using an identity WHERE clause ... which doesnt exist. Links in to 1 above. Records can be deleted by SQL bulk delete statements.

Andy Jefferson made changes - 21/Apr/07 01:04 PM
Fix Version/s 1.2.0 [ 10021 ]
Priority Minor [ 4 ] Major [ 3 ]
Andy Jefferson made changes - 22/Apr/07 06:00 PM
Status Open [ 1 ] In Progress [ 3 ]
Andy Jefferson made changes - 13/May/07 01:57 PM
Status In Progress [ 3 ] Open [ 1 ]
Andy Jefferson added a comment - 12/Jul/07 08:24 AM
Moved from 1.2.0 since not essential for that release

Andy Jefferson made changes - 12/Jul/07 08:24 AM
Fix Version/s 1.2.0 [ 10021 ]
Andy Jefferson made changes - 07/Aug/07 09:47 AM
Fix Version/s 1.3.0 [ 10262 ]
Andy Jefferson made changes - 21/Dec/07 06:36 PM
Assignee Andy Jefferson [ andy ]
Andy Jefferson made changes - 30/Mar/08 01:30 PM
Fix Version/s 1.3.0 [ 10262 ]
Andy Jefferson made changes - 23/May/08 03:06 PM
Project JPOX Core [ 10000 ] DataNucleus Core [ 10143 ]
Key CORE-2132 NUCCORE-25
Component/s Lifecycles [ 10156 ]
Component/s JDO [ 10000 ]
Affects Version/s 1.0.1 [ 10005 ]
Andy Jefferson made changes - 09/Apr/12 01:52 PM
Project DataNucleus Core [ 10143 ] DataNucleus Store RDBMS [ 10144 ]
Key NUCCORE-25 NUCRDBMS-586
Component/s ORM [ 10141 ]
Component/s Lifecycles [ 10156 ]
Andy Jefferson made changes - 09/Apr/12 01:52 PM
Attachment testcase.zip [ 10402 ]
Andy Jefferson added a comment - 09/Apr/12 02:33 PM
SVN trunk has this

Andy Jefferson made changes - 09/Apr/12 02:33 PM
Status Open [ 1 ] Resolved [ 5 ]
Assignee Andy Jefferson [ andy ]
Fix Version/s 3.1.0.m3 [ 11543 ]
Resolution Fixed [ 1 ]
Andy Jefferson made changes - 14/May/12 07:45 PM
Status Resolved [ 5 ] Closed [ 6 ]