Document databases (or textual databases, for that matter) simply aren't a good fit with the relational model Well, one might argue also that hierarchical data is also not a good fit with the relational model. Or what do you think about "hacks" like Materialized Path or Nested Sets model, or even native XML data type? If we already have XML data type in many DBs, what prevents us having Document data type like what's in CouchDB (yes, it's proprietary, but so are many of the features in current RDBMS). MySQL is also backend storage engine agnostic and it has already a support for many different (and somewhat specialized) backend storages engies (MyISAM, InnoDB, MERGE, MEMORY (HEAP), BDB, EXAMPLE, FEDERATED, ARCHIVE, CSV, BLACKHOLE and ISAM...). Is there a change that something like CouchDB would fit in that? Damien Katz has for example said that he might consider supporting SQL syntax, but it's too early to say.
In fact even this 1/77.1 doesn't work. So the bug isn't 65,534-bug, it's floating point bug. I even re-checked the calculations with Microsoft Calculator.
I use Robocopy on Windows to backup my stuff on USB drive. It has an option to run on background. Robocopy synchronizes continuously. I run it as a scheduled task with separate user account (the tasks is set up to start on boot). It continues to work even if I take off my USB drive and attach it back later. It takes about 2 MB of memory and doesn't need much cpu. Robocopy does not have versioning capabilities. On *nixes I prefer rsync or rdiff-backup.
Slashdot Mirror
Will MySQL consider positioning itself for Document Databases too (http://couchdb.org/) (Damien Katz works for MySQL: http://damienkatz.net/2004/12/about-me.html).
"So the bug isn't 65,534-bug, it's floating point bug" To be honest, it's very likely that there are many bugs.
In fact even this 1/77.1 doesn't work. So the bug isn't 65,534-bug, it's floating point bug. I even re-checked the calculations with Microsoft Calculator.
This doesn't work either: =850/(1/77.1) So they have to disable the divide-operation altogether.
I use Robocopy on Windows to backup my stuff on USB drive. It has an option to run on background. Robocopy synchronizes continuously. I run it as a scheduled task with separate user account (the tasks is set up to start on boot). It continues to work even if I take off my USB drive and attach it back later. It takes about 2 MB of memory and doesn't need much cpu. Robocopy does not have versioning capabilities. On *nixes I prefer rsync or rdiff-backup.