New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to CDO 4.2 #68

Closed
jutzig opened this Issue Nov 30, 2012 · 1 comment

Comments

Projects
None yet
1 participant
@jutzig
Owner

jutzig commented Nov 30, 2012

The reason the Database grows so large is this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=351068
Apparently objects will never be deleted when in non-auditing mode in CDO 4.0.
Since we're operating in non-auditing mode the tables just keep getting bigger with each new scan/change.
We should move to CDO 4.2 ASAP.

@jutzig

This comment has been minimized.

Owner

jutzig commented Dec 1, 2012

I tried the integration build of 4.2 and it seems to work fine, but unfortunately it also requires an integration build of EMF 2.9

jutzig added a commit that referenced this issue Dec 1, 2012

#68 : Move to CDO 4.2
temporary workaround until CDO 4.2 is actually released. I added
database cleanup code into the CDO Server Activator that deletes all
stale objects before starting up the repository.
Might make sense to do this in a scheduled job instead to clean the DB
on a regular basis

@ghost ghost assigned jutzig Dec 15, 2013

@jutzig jutzig closed this in 0cc30dc Dec 15, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment