Hi, I have been getting up to speed on db4o and I have started implementing storage. I would like to know whether I should continue my quick and dirty conversion of the in memory storage (as a sort of "tech preview") or whether people think it would be better to do something that uses more of the inbuilt functionalities. I ask this because the in memory implementation, for example, just goes through all the items in a collection (which is our equivalent of a table) and stops when it gets to the desired object. What I have done so far is just to get and then persist a collection to file - using the same code to find values. It is much more efficient to use the query facilities available... but means a lot less copy/paste! For info, db4o has a replication module which I think could be very useful for migrating from one machine to another... What do people think? Cheers Anton
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Alchemi-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/alchemi-developers
