If all phone manufacturers could just ship their Android devices with an sqlite3 executable installed, my day would be so much easier.

Explain?

@clovisIrex the Android API has built in support for sqlite databases. So you can execute queries from an Android app in order to read from and write to a private database that only your app has access to. For debugging purposes, emulators (and some devices if I understand correctly) has an sqlite cli executable that you can access through the adb shell. That would be a very convenient feature to have on the devices I use for debugging.

Now I kinda just have to print the tables in the logs if I want to be able to see the actual contents of them.

If your using Cordova or webview apps you can just inspect it through Chrome?

@ganey I'm developing a native Android app using Android studio. If I could at least just run an emulator, that would help a lot. But my CPU at work doesn't support Vt-x.

Ahh yeah, that sucks :( I'd keep complaining about your pc. I eventually got a lovely new one with more ram and a better CPU!

I know that that the Android API has sqlite support, but it doesn't make sense that it has no sqlite executable for debugging.

If you root a device and look for it in a terminal, it isn't there?

What about connecting to an sqlite instance remotely? Can you make the Android device listen for connections in an open port through code or configuration and acesss it with some kind of sql editor?

@clovisIrex there are guides on how to push the executable to a device but I'm too lazy for any solution that will take me more than five minutes. I just wanted to rant about it instead.

@Olverine
You sound alot like me. I'm always too lazy to work on my self projects so I rant, shitpost and watch tutorials instead.