Hi, is anyone still working on this? I just noticed it's actually quite an old topic, but I can offer some ideas / response / help perhaps.
I'd prefer if reports were inserted automatically and there were options to control how many or how long to keep a history of. Perhaps something like delete reports older than 1 month except to keep 1 full report for each day or each week so you can do time graphs if you wanted. Lots of people like stats I think

Also I'd like to be able to do a search on say inactive player planets near my colonies that showed resources from a recent scan, and defenses from another earlier scan if the most recent report didn't have that info. And I'd like to see the activity you get in the report that says 48min ago someone scanned it or whatever, so you can decide where to attack that hasn't recently been scanned, perhaps. (I dunno - just started OGame 4 days ago).
As far as the archiving goes, you could minimise space by storing the different sections of the reports separately e.g.
ReportResources table - linking to Reports, containing resource values
ReportFleets - linking to Reports containing fleets info
ReportDefenses - linking to Reports...
ReportBuildings - linking to Reports...
Reports table with date, user, etc, and fields like ReportResourcesID, ReportFleetsID, ReportDefenseID and ReportBuildingsID
Reports with just resource info would take little room this way, but it’s a trade-off with the overhead of linking the data and code complexity I guess.
Also you could put fields in the Galaxy table containing the IDs of the most recent Resources/Fleets/Defenses/Buildings info so it's quick and easy to get the most up to date data for a planet which may originate in different reports.
I'm thinking a compound key of scantime (as datetime) and galaxy+sysem+planet might be useful for those 4 tables. Duplicate keys wouldn't be a problem I don't think - if a 2nd report from another user for the same planet at exactly the same time arrived, it could just link to the existing report detail records I guess, since you’d expect the info to be identical. If this type of key was used, you could use the scantimes instead of an IDs in the galaxy table to link the most recent Resource/Fleet/Defense/Building info. I guess you could further save space by having an ID for galaxy records and using that instead of galaxy+sysem+planet.
It could also save some space if the planet name and other common info was recorded only in the galaxy table, and not in the reports table as well, but I guess then you'd have no way to track planet name/ownership changes then.
One alternative would be to have a table like PlanetOwnership or PlayerPlanets or something to record the name of the planets and who owns them. It could reference galaxy table and be referenced by reports, so there wouldn't be 1000s of varchar records in the reports. Would make it easy to see the history of a planet which changed hands a few times, if there was a record with a date for each time it was colonised/renamed/abandoned. But again space saving vs complexity I guess. Kind of makes sense though I think, having a table (galaxy) for the actual planets, another to record the ownership details of those planets which is referenced by reports and report details that contain only minimal data.
Is that the sort of thing you wanted to discuss when you wrote that? Hope so

. Perhaps it's already done. I haven't really thought it through much, just some ideas.
Actually I started doing something similar yesterday, separating the report details, then I realised that only 1 report was saved for each planet - bummer. Anyway, here's the sql I was using to change the scantime to datetime datatype which might save you a couple of minutes if you haven't already done something similar
update capella_reports
set scantime2 =
Cast(
If( (Length(scantime) < 14),
# scantime is blank or something unexpected, use zero datetime
'0000-00-00 00:00:00',
If( (Length(scantime) = 14),
# assume scantime is mm-dd hh:mm:ss format, prefix the year
Concat(Year(Now()), '-', scantime),
# Length(scantime) > 14
# assume it's yyyy-dd-mm hh:mm:ss, just use unmodified value
scantime
) #end if
) #end if
as datetime)
v4_5_3 btw
I'd be happy to help out with the SQL side if you can use any help there. I don't know any php, and only used MySQL for the 1st time yesterday, but I've used SQL a fair bit in SQL server and stuff. I'm interested in getting a report that shows recent resource info with older defense info. For me, SQL/DB side won't be a problem I don't think, but changing the php will. I don't suppose you've got a version that keeps multiple report records lying around anywhere that I could get hold of do you?
[Edit]Ah, I just read that galaxy tool isn't open source - sorry I shouldn't be changing stuff, I didn't realise before. I just assumed it was open source, probably coz all the source is installed. I can get rid of the code above if you like, but I thought I'd leave it just in case it's of any small use to you guys. I did wonder why there was no mention of an SVN repository anywhere though. I'd still be interested in helping, or getting a more recent version for my own personal, use to fiddle around with here if that would be ok? I'm just running it on my local computer and it goes without saying I'd not pass it on to anyone etc. I'm not sure how strict you guys are about it and understand if you don't want to do that, but I thought I'd ask all the same.