From Amarok Wiki
The main question most people (me, for example) would have, I guess, is wether switching to mysql offers any advantages over sqlite. I think this should be explained on this page.
-- And maybe how to set up the database, or a link to a helpfull place (although a "just type this in the console" -answer is easyer)
Contents |
Adding a mysql diagnostic test
When first set MySQL on, I didn't have any information of why the collection wasn't being created. A few problems appeared, like wrong password, wrong database... and a firewall opening a wrong port. I don't think I'm the only one in this case. Maybe an assistant for this would a great help, perhaps running as root to set the database up alone, or at least something that could indicate what is going on.
Plyd
- well, amaroK just needs to be more verbose about the problems it encounters. --Eean 14:57, 28 Jan 2005 (EST)
- Now when it runs into error on connecting to the database it will let you know about it. I added this a few days ago, so check out amaroK 1.2.1. :) --Eean 02:42, 27 Feb 2005 (EST)
No need to compile if you run a standard 1.2.3 binary from debian archives
Probably self-evident to most, but for some end users it may not be obvious that the MySQL capability is built into (at least) amaroK 1.2.3 from debian testing, and I assume other similar vintage distributions. So no need to build it from source if you want use MySQL.
- Could you clarify this for people on the page then? Thanks. --Eean 19:57, 11 May 2005 (EDT)
MySQL -> SQLite
I receive an error in sqlite, after running ".read amarok.sql":
<last few lines>
5'),(30,'1'),(31,'1981'),(32,'1995'),(33,'1985'),(34,'1992'),(35,'98'),
36,'1998'),(37,'1966'),(38,'1988'),(39,'99'),(40,'1970'),(41,'1991'),
(42,'1993'),(43,'2'),(44,'1957'),(45,'1967'),(46,'0'),(47,'1982'),
(48,'1976');
SQL error: unrecognized token: "`"
UNLOCK TABLES;
SQL error: near "UNLOCK": syntax error
sqlite>
How to handle this?
Cheers,
Jeroenvrp 17:56, 23 November 2005 (EST)
Changes to the SQLite -> mySQL script
I had mySQL running when I installed Amarok, and even though I told it to use mySQL, it apparently didn't listen. I didn't realize this until after I'd already spent some time matching albums to album labels & such. Since I wanted to convert my entire SQLite database, and not just the statistics, I played around with the "unsupported" script.
I probably should have rewritten the perl substitutions in sed, but honestly, I normally do command line substitutions using perl anyway. The VARCHAR(256) was absent in my dump file, so I dropped that line.
The rest worked fine, except that Amarok somehow had imported one of my albums as having the title "\", which mySQL didn't much like.
So I made some changes to the article to reflect this...
<opinions>
I still don't think that Amarok quite matches WinAmp's media library in terms of ease of use and intuitive-ness. I'd accidentally ripped an album in Mpeg4 format and Amarok -even though it can play them- doesn't read the tags and refuses to include them in my library. Actually, there are many, many areas that Amarok and other Linux media players fall short of WinAmp, but as far as what's available in Linux for playing audio, Amarok seems to be the better option.
</opinions>