Christopher Browne
Christopher Browne
These were interesting Emacs additions...
Schemaverse requires (there are several references inside pl/pgsql code) that the "owner" user be called 'schemaverse', and that it be a superuser. I'd somewhat like for neither to be required....
Here is a "drafty" form of drawing location off of the main ship table to a separate ship_location table.
Splitting them into separate tables allows handling the queries quite a lot more efficiently. Notably, instead of having a (nasty-to-performance, Seq Scan-inducing) series-of-OR clauses in my_event, it becomes series of...
Creation of new ships is frequently causing my scripts to time out, and this seems to fall from the insert into ships_near_ships. https://github.com/cbbrowne/Schemaverse/commit/414228445f3dc73c965730de52fbb73098d4f08d
It would be a good idea to add in a regression test that: - Sets up the database from scratch - Adds a few players - Makes them do some...
The view is a bit too much of a many-way join. https://github.com/cbbrowne/Schemaverse/commit/e1a3877e3de952fa7d6d1cc3ca915d207518dd04 I suggest adding player # to the ships_near_ships table; given that, access to this data becomes _way_ more...
I have been finding queries against my_ships to be extremely slow. An EXPLAIN shows why, pretty clearly: [email protected]> explain select \* from my_ships; ## QUERY PLAN Hash Join (cost=12653.52..13744.93 rows=2070...
Nice to have stuff... This adds a log entry each time a fleet script runs https://github.com/cbbrowne/Schemaverse/commit/6bc76edc589a6c5eaba204b7bad93273771c7a94 This adds in how long it took for your fleet script to run https://github.com/cbbrowne/Schemaverse/commit/06d6d128f6b0455fd566554735bb6db80b137030
You have set up a way of having hooks to do sophisticated fleet policy management, which is excellent. I think it would become more convenient to program the fleet if...