On 12/11/05, Geoff B <[EMAIL PROTECTED]> wrote: > > Have you considered leveraging the existing SQLite DB instead? > Instead of creating a .moo file, couldn't you just use existing > drivers to use the already-scanned data, like this one: > http://adodotnetsqlite.sourceforge.net/documentation/csharp_example.php > > Of course, it would mean that the user would need to copy the .db file > to any remote computers that would be running Moose, but presumably > that is no different to copying the .moo file, right? Or am I missing > something fundamental here?
Hi Geoff, Yes, this is pretty much what I'm hoping to do next, although I'm probably going to keep with the .moo files (size/speed), and access the .db file either over the network, or copied locally, as you say. That link you sent looks rather interesting. I was actually going to implement MySQL support first, but I think you've just changed my mind.. :-) Hopefully the code will be pretty similar for either.. I think database access is definitely the way to go.. It'll mean Moose will be able to do stuff like sorting by years and genres, and also the telnet traffic should be reduced a bit as it'll all become ID-based rather than path-based.. -- - Dr Lovegrove http://www.rusticrhino.com/drlovegrove _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
