Additionally, you can dump the complete database content into csv files, one per table, including column headers. There's a way to start the dump from the script console, but I forgot which command it is exactly. They'll be in your home directory. For even more fun, you can magically configure Amarok to dump the database at various points during the collection scanning process (unless that got removed during a refactoring at some point).
Cheers, Max On Wed, Jun 15, 2011 at 4:52 PM, Bart Cerneels <bart.cerne...@kde.org>wrote: > On Wed, Jun 15, 2011 at 16:32, sandeep <sandy.8...@gmail.com> wrote: > > Hi, > > Is there any way to see what tables exist in the embedded database used > by > > Amarok and the columns in those tables? Is it documented? > > Thanks, > > Sandeep > > DatabaseUpdater::createTables() is what you need. It's not better > documented than in the code. > Ask on this list if anything is unclear. > > Bart > _______________________________________________ > Amarok-devel mailing list > Amarok-devel@kde.org > https://mail.kde.org/mailman/listinfo/amarok-devel >
_______________________________________________ Amarok-devel mailing list Amarok-devel@kde.org https://mail.kde.org/mailman/listinfo/amarok-devel
