tibia/querymanager - Tibia 7.7 compatible query manager

	Commit message (Collapse)	Author	Age
*	add include path for PostgreSQL + overall cleanup	fusion32	2025-10-19
\| \| \| \| \| \| \|	Some distributions place libpq headers under /usr/include/postgresql which is why it's added to the include path. And even though we don't support it yet, the same happens with MariaDB, with headers being placed under /usr/include/mariadb.
*	properly handle text encoding differences with QueryManager clients	fusion32	2025-10-16
\|
*	organize database configs and schema files + compilation guards	fusion32	2025-10-10
\|
*	sketch out new query queue/worker for async queries	fusion32	2025-10-06
\|
*	wrapping up for a public release	fusion32	2025-08-15
\|
*	store world hostname and resolve at runtime	fusion32	2025-08-08
\|
*	finish game queries	fusion32	2025-07-15
\|
*	house related queries	fusion32	2025-07-12
\|
*	implement more queries + overall improvements	fusion32	2025-07-11
\|
*	bare bones query manager	fusion32	2025-07-10
	This is a bare bones query manager that will respond just enough queries to get the server running. The overall structure of the tables should be almost set but we'd need to handle all queries to get the server running properly. It uses the SQLite3 3.50.2 amalgamation for a database backend so we can completely avoid having to spin up yet another service for a separate database system, effectively turning the query manager into the database itself. This also means that other services such as the login server and website must go through it to access the data but it shouldn't be too difficult to replicate the querying mechanism from the server. This design choice was made with a single game server in mind. The networking protocol is NOT encrypted at all and won't accept remote connections. For a fully multi-world distributed infrastructure, a distributed database system like PostgreSQL and MySQL should be considered.