Both forking sqlite, and disliking the forking of sqlite, are allowed.
Plus, it's just technically bad. Most cases where you'd want to scale up sqlite are better served by a client/server database.
Plus, it's just technically bad. Most cases where you'd want to scale up sqlite are better served by a client/server database.
But not all of them, right? I don't need scaling across different hosts, but I need scaling between different threads on the same host. And I don't want for that PostgreSQL, MySQL, Oracle an other stuff like that.