Community
Participate
Working Groups
We get more and more persistent system values like ID counters or branch counters and these values get more and more optional like ID counters for the coming client-side ID-assignment mode (UUIDs). We need to abstract concepts like initialization, get/set, inc/dec, crash recovery, etc.
In the DBStore ID counter recovery after a crash requires access to the complete mapping information to scan all columns that can contain IDs. Currently this is not possible, because crash recovery takes place before the store has finished its activation phase. Hence the CDOPackageLoader of the repository package registry does not yet work at this time. I'm investigating on ways to split the activation phase...
Committed revision 7030: - trunk/plugins/org.eclipse.emf.cdo.server
Committed revision 7031: - trunk/plugins/org.eclipse.emf.cdo.common - trunk/plugins/org.eclipse.emf.cdo.server - trunk/plugins/org.eclipse.emf.cdo.server.db - trunk/plugins/org.eclipse.emf.cdo.tests.db - trunk/plugins/org.eclipse.emf.cdo.workspace
Committed revision 7062
Moving all open enhancement requests to 4.1
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Moving all outstanding enhancements to 4.3
Moving all open enhancement requests to 4.4
Moving all open bugzillas to 4.5.
Moving all unaddressed bugzillas to 4.6.
Moving all open bugs to 4.7
Moving all unresolved issues to version 4.8-
Moving all unresolved issues to version 4.9
Moving to 4.13.