Reply to thread

Message

<blockquote data-quote="JulianBuss" data-source="post: 70173" data-attributes="member: 10499">donnow, maybe you can archive your goals with my modification. What I do in the background: I have one common SQL select statement used for all views (including the custom views):[code]select album.idAlbum,album.strAlbum,artist.idArtist,artist.strArtist,song.idSong,song.strTitle,genre.idGenre,genre.strGenre,song.iTrack,song.iDuration,song.iYear,song.iTimesPlayed,song.iRating,song.favorite,path.strPath,song.strFileName from song,album,artist,genre,path[/code]together with one common where clause:[code]where song.idAlbum = album.idAlbum and song.idArtist = artist.idArtist and song.idGenre = genre.idGenre and song.idPath = path.idPath[/code]and with a group by and order by clause depending on the first view level, for example for a view showing the genre first:[code]group by strGenre order by strGenre[/code]You can extend this automatically generated SQL by your own additions to the where clause, for example:[code]strGenre like '%Pop%'[/code]Because the select statement includes all useful information from all tables, you can add where clauses as you like. So as far as I can see your requirements should be doable. If not we have to talk again. But we have to keep in mind that this is quite a power feature for very specific users. It must not interfere with the simple way to define custom views. [/code]</blockquote>

[QUOTE="JulianBuss, post: 70173, member: 10499"] donnow, maybe you can archive your goals with my modification. What I do in the background: I have one common SQL select statement used for all views (including the custom views): [code] select album.idAlbum,album.strAlbum,artist.idArtist,artist.strArtist,song.idSong,song.strTitle,genre.idGenre,genre.strGenre,song.iTrack,song.iDuration,song.iYear,song.iTimesPlayed,song.iRating,song.favorite,path.strPath,song.strFileName from song,album,artist,genre,path [/code] together with one common where clause: [code] where song.idAlbum = album.idAlbum and song.idArtist = artist.idArtist and song.idGenre = genre.idGenre and song.idPath = path.idPath [/code] and with a group by and order by clause depending on the first view level, for example for a view showing the genre first: [code] group by strGenre order by strGenre [/code] You can extend this automatically generated SQL by your own additions to the where clause, for example: [code] strGenre like '%Pop%' [/code] Because the select statement includes all useful information from all tables, you can add where clauses as you like. So as far as I can see your requirements should be doable. If not we have to talk again. But we have to keep in mind that this is quite a power feature for very specific users. It must not interfere with the simple way to define custom views. [/code] [/QUOTE]

Verification