EVEmu Control Panel and other tools don't know what type of database is being accessed about evemu_server HOT 5 CLOSED

I believe there already is such a table, srvStatus. Now it contains only dynamic info about server, but can be expanded for static info as well. Just insert a value into it in evemu_static_dump.sql or something like that.

from evemu_server.

It seems to be good proposal, but I have to ask: who is still running Apocrypha and Incursion? Who would use this new feature in ecp and benefit from it? Control panel and other stuff should certainly be updated for crucible database, but is backward-compatibility really needed?

from evemu_server.

positron, I was thinking of not only backward compatibility, but for future as well.

My thinking is that it might be better if the latest codeline of the ECP app can work with any of the past databases just as well with whatever database is the most current used by the EVEmu server.

The other approach would be to maintain branches of the ECP application, one separate branch for each client version that EVEmu ends up supporting (in our case right now, only Apocrypha, Incursion, and Crucible).

I'll leave this open for more discussion. I did see there is a srvStatus table and we can fill it with whatever <string, value> pairs we wish to, such as client version, database version, machonet version, etc. Enough data for ECP to learn about the database to which it's connected and use appropriate query structure and interpret table data appropriately.

-- Aknor

from evemu_server.

If there is an "assign ticket to someone" button, I think I can handle this issue

from evemu_server.

as there is no updates on this, and it seems the control panel is no longer functional, this is being closed.
if this problem arises again, a new bug report should be filed.

from evemu_server.