I really don't get the "use sqlite in production" thing.

What about all the important things you need in a database such as multiuser/remote access and other such things?

What do the "sqlite in production" people do when they need to examine the database/resolve an issue/do development? Also what about the limitations of sqlite in modifying database structure?

▲

pythonaut_16 4 days ago | parent [-]

Do you actually need all those things?

The simple answer to your question is you don’t. And if you do need them you don’t use SQLite.

▲

procaryote 4 days ago | parent [-]

I'd say that for any non-toy service, the default is that you do need those things, and would probably be helped by a database that cares what type you said the column had

Can you even redeploy a sevice like this without downtime?

	▲	pythonaut_16 2 days ago \| parent [-]
		Do you need to redeploy your service without downtime? Do you need multi-user and remote access? Why can't you just use a copy of the database when you need to examine it or resolve issues? None of these things have anything to do with being a "toy" app or not. They are matters of scale and business requirements. But that's the point isn't it? There are plenty of non-toy systems where none of these requirements apply. Plenty of very successful business and applications could handle a brief downtime for deployment. Plenty don't need multiple users or remote access, plenty have reasonably small databases.