Appears to be good news and perhaps bad news. Will a migration strategy from MongoDB to a sql database still be provided? Despite some connector maintenance, it is clear to me from the discussion I have built on the wrong database. Like a bandaid, I am better pulling it off quickly than allow the database to keep ballooning.
Would suggest the planned update to the docs be brought forward to make it much clearer that there is a preference of one database type over the other. At the moment it looks like they are all treated equal. I’m sure it is frustrating for some people who built databases in the past, but nowhere near as frustrating as it will be for those starting a database today and only finding this post in a months time.
Personally, I feel you may be better off sticking with your original plan of removing support. Don’t get me wrong, this will be a huge pain for me. But probably better for everyone for Strapi to take a little bit of heat for a while than create extra work for now three organisations that in the long run, it’s bound to be detrimental to the masses. It also doesn’t provide an attractive scenario for those looking for the most stable platform when it relies on coordination across orgs like that, it would be very hard to suggest MongoDB as an option. I get the feeling you all talked each other into the idea of a hybrid continual support, when perhaps sticking to your guns may had been better.
With more info on and commitment to a migration strategy, the amount of that .4% severely affected would be reduced considerably.
Regarding the .4%, presumably people can disable the telemetry despite what database they use. All things equal, let’s assume as many people on SQLite disabled telemetry as MongoDB and so forth. Suggests .4% would be a relatively accurate number (although curious how many users that equates to but really that’s understandably an internal number ).