Reply to thread

Message

<blockquote data-quote="Lyxalig" data-source="post: 70169" data-attributes="member: 11286">I'm hoping this is going to help me out with my &quot;view&quot;-problems. Problems: I have a lot of singles that has album-tag because of it's origin, I have lots of compilation-albums, and I have&nbsp; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" /> uncomplete <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite10" alt=":oops:" title="Oops!&nbsp; &nbsp; :oops:" loading="lazy" data-shortname=":oops:" /> albums.What I'm looking for is a way to completely set the requisites for the views. As I know sql, I would find it very useful to be able to write my own sql-statements.Ex for config;Albumview-&gt; add new view: &quot;Compilations&quot;Albumview-&gt; add new view: &quot;Single artist&quot;The code for the first one would be:[code]SELECT idAlbumFROM albumWHERE inumArtists &gt; 1 [/code]And the second one:[code]SELECT idAlbumFROM albumWHERE inumArtists == 1 [/code]As I have &quot;Albums&quot; with only one artist (inumArtists == 1) some logic should be added to make sure this album has more than a few tracks.That renders the &quot;Single artist&quot;-album view code:[code]SELECT idAlbumFROM albumWHERE inumArtists == 1 AND idArtist IN&nbsp; &nbsp; (SELECT idArtist&nbsp; &nbsp; FROM song&nbsp; &nbsp; GROUP BY idArtist&nbsp; &nbsp; HAVING COUNT(*) &gt;=7) [/code]The views should have a sortby handeler as well, but in my opinon; Beeing able to fully customize the views would be awsome, as well as people who know sql could make custom-views for any user, and it can alsom be posted in a seperate list or something...BTW: I would love a list of views in the GUI to complement the changes, look something like this:Views-Album&nbsp;+Single artist&nbsp;+Compilation-Artist&nbsp;+ Favorites (lots of songs for example..)&nbsp;+ Old-timers (Earlier than ???)&nbsp;+ One-Hit-Wonders (One or two songs)&nbsp;+ Newcomersand so on.......What needs to be done?</blockquote>

[QUOTE="Lyxalig, post: 70169, member: 11286"] I'm hoping this is going to help me out with my "view"-problems. Problems: I have a lot of singles that has album-tag because of it's origin, I have lots of compilation-albums, and I have :oops: uncomplete :oops: albums. What I'm looking for is a way to completely set the requisites for the views. As I know sql, I would find it very useful to be able to write my own sql-statements. Ex for config; Albumview-> add new view: "Compilations" Albumview-> add new view: "Single artist" The code for the first one would be: [code] SELECT idAlbum FROM album WHERE inumArtists > 1 [/code] And the second one: [code] SELECT idAlbum FROM album WHERE inumArtists == 1 [/code] As I have "Albums" with only one artist (inumArtists == 1) some logic should be added to make sure this album has more than a few tracks. That renders the "Single artist"-album view code: [code] SELECT idAlbum FROM album WHERE inumArtists == 1 AND idArtist IN (SELECT idArtist FROM song GROUP BY idArtist HAVING COUNT(*) >=7) [/code] The views should have a sortby handeler as well, but in my opinon; Beeing able to fully customize the views would be awsome, as well as people who know sql could make custom-views for any user, and it can alsom be posted in a seperate list or something... BTW: I would love a list of views in the GUI to complement the changes, look something like this: Views -Album +Single artist +Compilation -Artist + Favorites (lots of songs for example..) + Old-timers (Earlier than ???) + One-Hit-Wonders (One or two songs) + Newcomers and so on....... What needs to be done? [/QUOTE]

Verification