Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359021 - [DB] resource.delete() does not remove actual data from the database
Summary: [DB] resource.delete() does not remove actual data from the database
Status: CLOSED DUPLICATE of bug 351068
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.db (show other bugs)
Version: 4.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-27 04:29 EDT by Missing name Mising name CLA
Modified: 2013-06-27 04:00 EDT (History)
1 user (show)

See Also:

Attachments
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 Missing name Mising name CLA 2011-09-27 04:29:21 EDT 
Build Identifier: CDO 4.0 Eclipse Indigo

Calling resource.delete() or EcoreUtil.remove over the contents of the resource and then comimitting the transaction does not remove actual data from the database. Instead, it just makes the resource unavailable from any client.

Reproducible: Always

Steps to Reproduce:
1. Store a model in CDO
2. Call resource.delete() and then transaction.commit()
3. Check the database: actual model data has not been removed
4. Model cannot be accessed by any CDO client
Comment 1 Eike Stepper CLA 2011-09-27 04:45:58 EDT 
From the newsgroup I got the impression that you're really talking about the HibernateStore. Is that the store you've encountered the removal issue with?
Comment 2 Eike Stepper CLA 2012-06-05 07:30:28 EDT 
Moving all open bug reports to 4.1 because the release is very near and it's hghly unlikely that there will be spare time to address 4.0 problems.

Please make sure that your patches can be applied against the master branch and that your problem is not already fixed there!!!
Comment 3 Eike Stepper CLA 2012-08-14 22:56:20 EDT 
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Comment 4 Eike Stepper CLA 2012-11-01 05:31:03 EDT 
Dup of bug 351068.

*** This bug has been marked as a duplicate of bug 351068 ***
Comment 5 Eike Stepper CLA 2013-06-27 04:00:35 EDT 
Closing