Nested Collections

[Landoman 28]

What are the issues? This is the single main feature I want.

[visproduction 374]

Nested groups using SQL dbase is a complex issue. Easy to describe, but difficult to code.  It's the "Easier said than done" type.  Most online sites do not offer this type of nested selection.  Even the search engines avoid it.  I can't think of an online example.  If you know of a site that does it, perhaps list it in this post.  It could be helpful.

Some details in general:
 https://www.geeksforgeeks.org/sql/nested-queries-in-sql/
 https://stackoverflow.com/questions/2872837/is-there-a-way-to-create-subdatabases-as-a-kind-of-subfolders-in-sql-server
 

Also, it's important that members click the heart or +1 icons on feature requests so popularity can be seen.  Consider, if rolling out a new feature might estimate as taking, say, 60 hours of dev time and perhaps ongoing support of say, 6 hours annually.  You multiple what dev hours cost and divide by how many users have agreed that the feature is a good one.  Then you get the cost per user who wants to use the feature.  Also important, is how easy would the feature be to market it as a bonus for the software?  I would imagine features may not be given the green light, if cost per user goes up too high.  It is easy to come to averages that are more than $1000 / user pretty quick. Finally, you don't really want to slow down the response time for anyone, so new features need to be designed to only kick in when a user clicks on it, and not have to run in the background, because that could slow other pages on the server.  That can be tricky to do.

Edited 17 minutes ago by visproduction