|
History
| Log In
|
|
|
|
Related feature: Batch activation for collections
We did the first spike for high speed writing. Times look very good when a small part of the collection is touched (dirty).
I would be really helpful be able to configure collections to add/remove items and also update the collection itself via container.set(...) so users don't have to update the items and collection explicitly via container.set/delete.
I have started a thread in our forums to discuss requirements:
http://developer.db4o.com/forums/thread/36773.aspx To all the people watching this issue: It would be great if you would post your requirements and thoughts to forums too. Thank you very much! Carl |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Fast Collections
(1) A very lean implementation for collections that contain a small number of objects.
(2) An implementation for large collections, maybe based on BTrees.
Ideally db4o would change the right type at runtime.