> I want to do some more tests to see if Tokyo Cabinet would really > offer much of a performance advantage -- and in what cases.
If you're doing simple get/put of data, it's going to blow any SQL server out of the water. But doing things like tables, foreign keys and joins is just not possible. I don't have any specific benchmarks, but I've seen tasks that take days on MySQL take seconds on DBMs like Tokyo Cabinet. The difference for simple data store can be substantial. You can certainly write a DM adapter. But you wouldn't be able to use most of the functionality. Even doing things like setting properties would be pointless. DM is an Object Relational Mapper, but since the database is not relational, the pieces don't fit. It's not to bash Tokyo Cabinet or DM, they're both great tools. They're just designed for fundamentally different things. Kyle Drake Net Brew Design http://www.netbrewdesign.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
