| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | fix small issue with TransferHouses queryHEADmaster | fusion32 | 2026-02-09 |
| | | |||
| * | change how guild data is stored | fusion32 | 2025-10-23 |
| | | |||
| * | 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 NULL values with postgres result helpers | fusion32 | 2025-10-18 |
| | | |||
| * | modify how automatic SQLite patches/upgrades works + overall cleanup | fusion32 | 2025-10-18 |
| | | |||
| * | world startup/shutdown timestamps + adjust a few column names | fusion32 | 2025-10-17 |
| | | |||
| * | properly handle text encoding differences with QueryManager clients | fusion32 | 2025-10-16 |
| | | |||
| * | move ResolveHostName outside of GetCharacterEndpoints | fusion32 | 2025-10-16 |
| | | |||
| * | lower monotonic uptime resolution from MILLISECONDS to SECONDS | fusion32 | 2025-10-16 |
| | | | | | | | | | | | | | The monotonic uptime was used exclusively with caches and having a resolution of SECONDS allows it to be stored as an int without risk of wrapping (~68 years). Using MILLISECONDS meant that it would wrap after ~25 days which is totally possible and EXPECTED. Just as an example, the small test server I ran for about 1 month had ZERO downtime on the QueryManager except for when I manually restarted it. It was probably very close to wrapping when I took it down. | ||
| * | gracefully handle no rows on "COUNT(*)" queries | fusion32 | 2025-10-16 |
| | | |||
| * | make config.cfg a distribution template | fusion32 | 2025-10-16 |
| | | |||
| * | fix a few postgres queries | fusion32 | 2025-10-15 |
| | | |||
| * | implement all postgres queries | fusion32 | 2025-10-15 |
| | | |||
| * | postgres interval helpers + a few more queries | fusion32 | 2025-10-15 |
| | | |||
| * | make query output parameter names more specific | fusion32 | 2025-10-14 |
| | | | | | | This also avoids conflicts with database RESULT objects that we lacked with SQLite but show up with PostgreSQL and MySQL. | ||
| * | GET_WORLD_CONFIG robustness + tidying up a few variable names | fusion32 | 2025-10-14 |
| | | |||
| * | the remainder of postgres helpers (probably) | fusion32 | 2025-10-14 |
| | | | | | | This should give us everything we need to implement all the supported queries. | ||
| * | more postgres helpers and a couple of queries | fusion32 | 2025-10-14 |
| | | |||
| * | most of the postgres primitives/helpers | fusion32 | 2025-10-13 |
| | | |||
| * | beginning of postgres driver + overall tweaks | fusion32 | 2025-10-13 |
| | | |||
| * | organize database configs and schema files + compilation guards | fusion32 | 2025-10-10 |
