Limit smart playlists ?

@riro wrote:

Is there any way to limit the smart playlists?

I want to create a playlist with my 100 last additions to the library…

Not currently. I’m finishing up the localization and backporting some of the fixes for the most annoying bugs into a 1.1 release for Roku, then I’ll be working on modularizing the database. That will come from that work.

But yeah, I want to do limits and custom sort orders for playlists.

Sweet idea 🙂

Hm nice to see how sqlite works different from ‘real’ SQL here.
I really have to dig up all those handy cron jobs, and add some polish to my slug somewhen 🙂

@riro wrote:

@rpedde wrote:

Oh, yeah… like that it’s doable. In fact, there’s no reason you could dummy up static playlists right in the database itself using sql queries (those are playlist type 0).

After a “few” days on the road Im back…

Did a few attempts to figure it out, but no luck.

What columns (any specific name/order) do you need to return from the query?

First, make your playlist:

foo@bar:~$ sqlite /path/to/songs.db
sqlite> insert into playlists (title,type,items,db_timestamp,idx) values (‘Recent Adds’,0,100,0,0);
sqlite> select last_insert_rowid();
154
sqlite> insert into playlistitems select NULL,154,id from songs order by time_added desc limit 100;

Note that once you have the id (154), you can just do the insert line. Or maybe your nightly cron job would do

delete from playlist items where playlistid=154; insert into playlistitems ...

Ooh. Except I just noticed a full rescan deletes those. I’ll fix that for next nightly.

— Ron

well 😉

sqlite> insert into playlists (title,type,items,db_timestamp,idx) values ('Recent Adds',0,100,0,0);

sqlite> select last_insert_rowid();

154

sqlite> insert into playlistitems select NULL,154,id from songs order by time_added desc limit 100; 

wow, that DB code looks weird.
is idx an auto-increment field? it should be a unique key anyhow. in oracle you do that with a sequence. anywho….

the statement

 insert into playlistitems select NULL,154,id from songs order by time_added desc limit 100; 

[/code]
looks weirdish too.

 INSERT INTO playlistitems

(SELECT NULL, 154, id

FROM songs

ORDER BY time_added DESC limit 100); 

that doesnt even look like proper SQL to me. you probably meant:

(SELECT id from SONGS ORDER by time_added DESC limit 100);

in that sub-select.

that deffo does a full table scan, since there are no indices.
I guess the last 100 indices of songs would suffice, since its a auto-increment field, or sequence of some-sort, right?

[/code]