Updating or deleting ‘linked’ records, like we do with SQL relationships on a database, can already be done in Kirby - even if it’s a bit of work, it can be done with hooks. But doing a QUICK SEARCH through 100,000 records simply can’t be done at all - and that is what we need. Let’s not even consider doing compound, boolean searches through multiple fields - in even just 10,000 records this can take more than 15 seconds. This means that Kirby can’t be used for sites that have tens of thousands (or more) of records, and there are a lot of sites like that. Like for example ecommerce sites with large product catalogs, community sites with thousands of users, blogs/forums with thousands of comments, photo galleries with thousands of images, etc, etc. It means that as a web developer, I can’t use “just Kirby” for all my jobs, and need to also know other CMSs that can handle large datasets with a fast database index. If I could just SEARCH QUICKLY through thousands of records in Kirby, I’d use Kirby for everything.