I can look into that. I already wrote the backend, it has a number of bugs, and it's really slow. The slowness is because I'm not doing enough work on waiting to see if I can do compound inserts rather than doing an insert every time. Basically, we need to support transactions.
Once you use a database you should be able to change the query language to address Jonathan's observations on it's limitation. I don't think the problem is insurmountable but it is a lot of work and probably should be branched as a separate project by those interested so that we can continue to maintain stable. sri On Sat, 2009-02-21 at 14:59 +0100, Gilles Dartiguelongue wrote: > Le vendredi 20 février 2009 à 13:26 -0800, Sriram Ramkrishna a écrit : > > This seems to be a limitation with having your own cross platform > > database. What about moving towards a different backend and then > > changing the query model to reflect that? > > > > I had thought about the same limitations myself, that was one of the > > things behind working on an sqlite backend. The query system was very > > good but somewhat limiting. Maintaing that portion I thought was > > somewhat burdensome. > > > > We have the basis of a patch, on the sqlite backend which seems to be > > pretty popular with a lot of music player applications. It would take a > > lot of pain but if we maintained the same api we could possibly get it > > right. > > > > sri > > If you want to move rhythmbox db to sqlite, please try to see what you > can do with libgda-3 or libgda-4 which are now blessed externals deps of > gnome (iirc). It will allow to replace crappy sqlite perfs (on some > systems) by something real, transparently for rhythmbox. > > _______________________________________________ > rhythmbox-devel mailing list > rhythmbox-devel@gnome.org > http://mail.gnome.org/mailman/listinfo/rhythmbox-devel _______________________________________________ rhythmbox-devel mailing list rhythmbox-devel@gnome.org http://mail.gnome.org/mailman/listinfo/rhythmbox-devel
