Linked by Mo Mckinlay on Fri 31st Oct 2003 17:35 UTC
There's been much discussion over the past few months about the marriage of databases and filesystems - with Microsoft's Longhorn reportedly sporting the
Yukon integrated SQL Server, and GNOME Storage in heaty debate, if not development, there's been lots to talk about.
Permalink for comment
To read all comments associated with this story, please click here.
Not necessarily... a database-backed filesystem could potentially make it more effort to implement proprietry file formats - after all, if you do store data in a strange way, you don't gain the benefits of database access to the files.
That said, it wouldn't suprise me in the slightest to see some sort of CRM implemented such that applications can specify what can and can't access a file using the database APIs.
Assuming that doesn't happen, for the moment, getting your data out of a file with an unknown format shouldn't be anymore difficult than extracting data from a database table with an unknown schema. Sure, it's not the easiest thing in the world, but it's far easier than decoding seemingly random streams of bytes with no apparent meaning.
Not necessarily... a database-backed filesystem could potentially make it more effort to implement proprietry file formats - after all, if you do store data in a strange way, you don't gain the benefits of database access to the files.
That said, it wouldn't suprise me in the slightest to see some sort of CRM implemented such that applications can specify what can and can't access a file using the database APIs.
Assuming that doesn't happen, for the moment, getting your data out of a file with an unknown format shouldn't be anymore difficult than extracting data from a database table with an unknown schema. Sure, it's not the easiest thing in the world, but it's far easier than decoding seemingly random streams of bytes with no apparent meaning.