SQLite VS phpMyAdmin

If you are into alternative storage engines for SQLite, there is also an LSM (Log-Structured Merge-tree) extension in the main repository that is not announced nor documented but seems to work. It’s based on the SQLite 4 project.

https://github.com/sqlite/sqlite/tree/master/ext/lsm1

https://www.charlesleifer.com/blog/lsm-key-value-storage-in-...

The sqlite code base is really well done. Lots of documentation.

https://github.com/sqlite/sqlite

Especially the VM part: https://github.com/spandanb/learndb-py/blob/master/learndb/v...

Compare it with this: https://github.com/sqlite/sqlite/blob/master/src/vdbe.c

That's said, I'm curious how complete this LearnDB is. SQLite is hard to read not only it's old but also it covers a lot of SQL and following SQL spec makes hings complicated. SQLite has great test suite so it's nice if you run the suit against this implementation.

"C in a Nutshell 2nd Ed" (O'Reilly, Prinz & Craqford, 2015) is a good reference although maybe not the best for a walk-through learning experience. It also has good chapters on tooling (gcc, make, gdb).

There's a recent book out I came across called "Bare Metal C" (No Starch Press, Oualline, 2022) which unpacks embedded programming in a very readable manner. I imagine a lot, if not most, C programming these days is done in the low-level embedded world, and this book clears up a lot of the mysteries.

https://nostarch.com/bare-metal-c

Also it never hurts to look at a good open-source codebase written in C, for example the SQLite code is worth looking at (if a bit overwhelming):

https://github.com/sqlite/sqlite/tree/master/src

> After that, 510 bytes are used for the SHARED lock. A byte range is used here to accommodate older Windows versions with mandatory locks.

I was curious how old, and... wow, that code is for Windows versions that predate the NT kernel (Win95/98/ME). I'm surprised that it's still around, but the comment does a great job of explaining it.

https://github.com/sqlite/sqlite/blob/3cf46ee508e97b46736a26...

I wouldn't rely on Google to learn good practices for technical documentation (unless they want to release their complete internal technical documents on how their recommendation algorithms work, that is).

Instead, check out a reliable open source project like SQLITE, they have great documentation:

https://www.sqlite.org/arch.html

https://github.com/sqlite/sqlite

Mastering SQL is like engaging in a deep conversation with databases. Sometimes, you might feel like you're "chatting" with data. But don't worry, tools like phpMyAdmin for managing MySQL databases ensure that your data stays put, bidding farewell to the nightmare of "lost data." This phase requires mastering SQL and relational databases like MySQL, using tools like phpMyAdmin for data management and optimization. Tools to consider: phpMyAdmin, MySQL Workbench, Sequel Pro, and other database management tools.

phpMyAdmin is the stalwart of free open-source database managers. It’s been around forever, and it’s just plain good at what it does — providing a graphical interface for fully managing every aspect of MySQL databases. It’s built using PHP and runs in the browser.

phpMyAdmin was born in 1998, written in PHP, and is a classic SQL client. It was the default tool for LAMP and MAMP at that time. phpMyAdmin has grown to become one of the leading tools for managing MySQL and MySQL-like databases (e.g. MariaDB) It has over 200,000 direct downloads per month (and countless other users install it using prepackaged installations or using package managers).

Is a Docker WordPress Environment focused on the development of WordPress plugins and themes, supports WP-CLI, phpMyAdmin, Xdebug and WordPress Coding Standards - WPCS.

I have been using it for years and while it is a resource hog and it occasionally crashes, I have not found it to be burdensome. You could always set up phpMyAdmin which IMO is sort of antiquated and a true PITA.

phpMyAdmin (DB management )

phpMyAdmin - SQL Database Viewer

We can do a quick check to see which versions we got, even without file system access. We can even install phpmyadmin (temporarily) as a wp plugin.

CVE-2016-6620 - "code exec" - https://github.com/phpmyadmin/phpmyadmin/commit/ba072e4 The patch shows unserialize is only used for parsing a schema snapshot (and "code execution" using this vuln is a stretch, you can run a class destructor with arbitrary variables and destructors rarely do anything exploitable)