Add more filters/views (please tell me which ones you want)

[logicalup]

So far I have gotten requests for: Location - separate view: search by location name, get: Mouse - Phase - AR Mice groups (indigineous for example) Loot search by mouse Mouse search by loot

[logicalup]

also need a view/filter for loot

Edit: done

[logicalup]

added loot view, and map mice view

[logicalup]

also filter by dates

[logicalup]

loot view per catch

[logicalup]

attraction rates by location per cheese

[logicalup]

so one possible time filter is to aggregate last 24 hours, and last week, last month. ( in addition to current all time.)

[logicalup]

added 3 day filter, and event filters. Also need to add filter for: "all encounters" and "at least 100 encounters"

[logicalup]

Let the user specify if they want bigger minimum. Can be done by aggregating on minimum 1 attraction and recording the number of attractions in the aggregated table. Then adding an integer field to the view and passing user choice to the server query. Leave the defaults to what they are now.

[logicalup]

all except events filter

[AardWolf]

I used this query to exclude all events recently.

from loot, mice, locations, hunts, hunt_loot, filters
where loot.id = hunt_loot.loot_id
and mice.id = hunts.MOUSE_ID
and locations.id = hunts.LOCATION_ID
and hunt_loot.hunt_id = hunts.id
-- The main part for excluding event hunts
AND filters.START_TIME IS NOT NULL
AND hunts."TIMESTAMP" NOT BETWEEN filters.START_TIME AND FILTERs.END_TIME
AND hunts."TIMESTAMP" < (SELECT min(filters.START_TIME) FROM FILTERS WHERE filters.START_TIME IS NOT NULL AND filters.END_TIME IS NULL)
-- end excluding event hunts
AND loot.name <> 'Treasure Map Clue'

GROUP BY loot.name, mice.name, locations.NAME
;

Not sure how you're writing your SQL (I could look at the code, I guess) but I can translate this to a few flavors if needed - EXCEPT, as inner join, or other ways. The EXCEPT syntax might be easier to add to existing query generation logic.

[PersonalPalimpsest]

added 3 day filter, and event filters. Also need to add filter for: "all encounters" and "at least 100 encounters"

Let the user specify if they want bigger minimum. Can be done by aggregating on minimum 1 attraction and recording the number of attractions in the aggregated table. Then adding an integer field to the view and passing user choice to the server query. Leave the defaults to what they are now.

Not sure if this is still being considered, but I think it would be good to have a minimum hunts filter field, since results get cluttered with low accuracy data from the few hunts that are done with empowered cheese/event cheese/wrong area cheese.

A filter for cheeses in general would be good too, if one doesn't want to use SB/magic essence cheeses.