Hi guys, For Sequoia testing can I suggest we focus on Derby as the default? At this point Hypersonic does not seem as if it has much of a future. We've also had a lot of issues with it for recovery logs. Derby by contrast has very good support from Sun and is continuing to move forward.
Cheers, Robert On 4/15/08 2:22 PM, "Emmanuel Cecchet" <[EMAIL PROTECTED]> wrote: Stefan, >> I was thinking that databases could be contained in virtual appliances >> so that we can easily start/clone/kill the virtual machines. >> > That was also one of my first thoughts some time ago, i did some work on > it, but i ran into problems with the time synchronisation inside the > VM's even when using VMware-Tools. But maybe it was cause of my debian > OS in the vmwares. > > Which OS you suggest as basis for a Test-DB-Node? > I was planning on using Fedora core with Xen as it is well integrated. VMWare is also an alternative but it is not open source nor free to use. I guess we should have a virtualization wrapper so that we can plug Xen or VMWare (or anything else). We will probably need specific daemons for fine grain synchronization but for now we can just plan on simple coarse grain operations. Using embedded databases such as Derby or HSQL can also be useful for a bunch of tests with a very fast setup time. I guess we can reuse some of the test suite that was developed in C-JDBC and later dropped in Sequoia. What where the synchronization issues you had to face? Cheers, Emmanuel -- Emmanuel Cecchet - Research scientist EPFL - LABOS/DSLAB - IN.N 317 Phone: +41-21-693-7558 _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia -- Robert Hodges, CTO, Continuent, Inc. Email: [EMAIL PROTECTED] Mobile: +1-510-501-3728 Skype: hodgesrm
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
