Summary: | database backends should be plugins loaded at runtime | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | fleona |
Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | contact, gauret |
Priority: | NOR | ||
Version: | 1.2.2 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
fleona
2005-03-23 22:28:30 UTC
In other words, you're asking for the database support to be moved to a plugin, loaded at runtime. That would also allow multiple backends possible. Exactly. Not easy to do, but this will benefit the whole project. That's why i put it as a wishlist There was some talk of doing this on amarok-devel SUSE ships amarok without mysql support built in because of this issue -- they want to avoid the dependency on mysql. Their answer to my wish to include mysql support was: "We do not want to have mysql (or postgresql) dependencies in our default installation. A proper way to solve this would be to add a general QSql engine to amaroK, so the user can select the database via the Qt plugins." Maybe this is a good way to solve this problem. Does Qt always have QSql? I read that the individual sql drivers are runtime plugins, I'm just wondering if qsql api itself is always included. On SUSE system, there is a qt3 RPM, a qt3-devel RPM (including qsql headers), and for example a qt3-mysql RPM (including the mysql drivers for qsql). To me it looks like the qsql api is always included, and the different drivers are included in seperate RPMS. Probably this is not only true for SUSE system. They are plugins in 2.0. |