Sorry I do not know how to do that with this db. The db has pragmas that treat the new table as "duplicated songs" and they appear to force "rowid" as the index value. Sorry I am not experienced in SQLite or using SQL. Not sure if anyone has successfully modified these without manually editing each record individually.
On Sunday, November 20, 2016 at 6:18:12 AM UTC-6, Alex Bikadorov wrote: > > > Don't know about the error. But if the tables are really identical, why > don't you replace > the old one with the new table (DROP + ALTER TABLE)? > > Alex > > > On 19.11.2016 21:39, Harpo3 wrote: > > I found this syntax is supposed to work: > > > > update songs > > > > set lastplayed = (select songsnew.lastplayed > > > > where songsnew.filename = songs.filename) > > > > where > > > > exists ( > > > > select * > > > > from songsnew > > > > where songsnew.filename = songs.filename > > > > ) > > > > > > but it does not work. The error message says: > > > > no such column: songsnew.lastplayed: update songs > > > > > > > > This is odd. When I type this into the SQLite database browser, it > correctly identifies > > the column. > > > > > > > > On Thursday, May 5, 2011 at 12:28:00 PM UTC-5, at wrote: > > > > how does clementine save this data? is it similar to the way that > > amarok 1.4 did in a mysql database? Is there a way to export amarok > > 1.4 playcounts/last played dates (and other stuff) to clementine? > > > -- You received this message because you are subscribed to the Google Groups "Clementine Music Player" group. To unsubscribe from this group and stop receiving emails from it, send an email to clementine-player+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
