| 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 |
| | | |||
| * | 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 |
| | | |||
| * | prevent a few SQLite queries to fail when they affected no rows | fusion32 | 2025-10-16 |
| | | | | | | | | This was done with the old design in mind, but with the query thread offloading, returning false is meant to signal a failure in completing it. A connection lost with PostgreSQL or BUSY error with SQLite, for example. | ||
| * | 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. | ||
| * | implement all postgres 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 |
| | | |||
| * | 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 |
| | | |||
| * | switch to blocking poll + fix config, signals, time, non-game login | fusion32 | 2025-10-10 |
| | | |||
| * | small indentation adjustment | fusion32 | 2025-10-09 |
| | | |||
| * | update sqlite driver + impl INTERNAL_RESOLVE_WORLD | fusion32 | 2025-10-09 |
| | | | | | | | With this change the game server is able to login again but we still need to re-implement/re-fit the other queries for it to properly startup. | ||
| * | worker initialization robustness + query processing | fusion32 | 2025-10-07 |
| | | |||
| * | make connections properly handle async queries | fusion32 | 2025-10-07 |
| | | | | | | | This moves queries from `src/connections.cc` to `src/query.cc` and adds a few missing details. The only thing left is to review query processing and tie database operations to the `TDatabase` struct. | ||
| * | sketch out new query queue/worker for async queries | fusion32 | 2025-10-06 |
