Ticket #355 (closed enhancement: wontfix)

Opened 2 years ago

Last modified 23 months ago

Common SQLite Audio DDBB

Reported by: nobody Owned by: theli
Priority: minor Milestone:
Component: Other Version:
Keywords: Cc:

Description (last modified by theli) (diff)

This is an idea that is around my head some time ago. We have a lot of Music players using sqlite to keep the Music info. So why dont use a common DDB for all player? Thsi can be great to help the user try other players. And common tools of optimization, recovery, import/export, etc.. can be used for all players.

Just a very initial idea:

Use 2 tables. one for "generic data" (titles, artist, etc etc) common to aall players. And another one with "specific data" to use by players with unique features not aviable in other players. The idea is to have all possible data in the "generic table".

This can be a nice freedesktop project rigt?

i will open a bug in several projects bug systems.

Change History

Changed 2 years ago by theli

Logged In: YES user_id=1463559

I not interested at all, i have remove sqlite from my project in version 0.5x because is slow and is not thread safe. i prefer use Pickle module of python to load and save directly python object(very simple to use and very fast)

I'am prefer work a common format to import/export db data if freedesktop want help migration between audio player.

Changed 23 months ago by theli

  • status changed from assigned to closed
  • resolution set to wontfix
  • description modified (diff)
Note: See TracTickets for help on using tickets.