Hi George Have you looked at SQLite? I use it to catalog my files and find out where the little so-and-sos are! I use Rexx to do all that stuff. I have a rexx snippet that will track file creation/modification/delete. Unfortunately, I do not know how to adapt it for my system so I have to do a periodic refresh of the table.
I have another problem with SPFLite but....cannot remember exactly what it is or even if it is a real problem! I think it my be text-flow when the left bound is not column 1 - still flows through column 1. I will get back to you when i have investigated and compared. Regds Nic -----Original Message----- From: George Georgalis <geo...@galis.org> To: netbsd-us...@netbsd.org CC: sqlite-users@sqlite.org Sent: Mon, 7 Jun 2010 3:50 Subject: [sqlite] sql api for ufs Subject says it all. I'm looking for a sql (like) api for ufs. I'd like to SELECT by device, inode, size, group, etc. If all the fs stat data was the db schema, I'd like a query engine that makes indexes of the meta data for fast queries, access to the file data, and queries of offline devices, when their index is available. I've never heard of an engine built specifically on top of a filesystem for interchangeable use via db api or as regular files. Of course I don't mean philosophically, which we already have, I mean something tight that uses modern db optimizers and enables dual access. A key features would be: - "exactly" the same data/time available via either fs or db queries - Race conditions are avoided through standard practice (atomic process) - Leave the task of journaling etc to the OS - Continuous and simultaneous use of either access mode. Extended features might include: - additional meta data like mime, "tags" and "notes" - additional device descriptors, such as hostname and protocol - file path info (I don't think this is part of the stat schema) - Sure this could be executed in a nosql like manner. I think the extended features could easily be implemented as filesystem data, eg if a device has a particular name, get the proto/host/path data from a file that is on a local dev, perhaps even the db index itself. So, has anyone heard of something along these lines? I think this is fundamentally a pretty simple task. Is there any obvious limitation or complexity I'm missing? I welcome comments off line or to either of the lists I'm posting to (but please not both). -George _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
