this what I mean, what if the author has much more than 100 book (or post in a social media site)?
1 Like
Haven’t fully grasped the issue of this thread but regarding your question on listfields, it is said that it has a hard cap of 10k things on them but Bubble suggest you keep only 1000. However, most bubblers would argue to keep it at < 100 for optimal performance.
In the event that you think your list would contain a lot of things, you should create/change it into a new datatype instead
Iread in bubble reference that you have to keep it at < 100 for optimal performance and you should create a new datatype instead.
but my question was how to sort in this case with multi DataTypes
100 is kinda low IMO. At least nowadays. 250 ish. Certainly not 1000.
So, what are the chances of an author having 100 books? Low but not impossible. 250? Highly unlikely.
In this case I would stick with the list, and ignore the occasional edge case.
However if this was the case, and I absolutely needed to have a primary screen that showed data like this, then I would de-normalise the data and store the name of the Author on the Book and then handle the (very very unlikely) situation where the author changes names.
But…if we are thinking about this deeply, then one author (a person) can have multiple names for the purposes of writing. Joanne Rowling the person is both JK Rowling and Robert Galbraith the author. And books have different names too (not just in different languages either).
So, we have a pretty complex set of search possibilities here. This is when Petter from Amlie Solutions talks about “Satellite Data Types”. Creating a specific, denormalised, index table that has all the names of books and authors.
Effectively a big “many-to-many” table with all the possible fields you want to search on.