Skip to content
This repository has been archived by the owner on Dec 7, 2022. It is now read-only.

Database should be toggleable #219

Open
hfoxy opened this issue Feb 20, 2015 · 6 comments
Open

Database should be toggleable #219

hfoxy opened this issue Feb 20, 2015 · 6 comments

Comments

@hfoxy
Copy link
Contributor

hfoxy commented Feb 20, 2015

The Database provided should really be off by default, and toggleable. That or other database options should be provided, by using an interface with many subclasses for different Database types. Storing player data in flat file will grow over time, and if the server is used a lot, it has the chance that the server may be slowed down by storing the large database document in RAM.

I can see that it is used for settings, and snowflakes, which personally I believe would be best stored in YAML, or in an actual Database, such as MongoDB or MySQL. Although ideally, for scrimmages, it should be off completely, unless of course you provide an open database for all Cardinal servers to use.

@twizmwazin
Copy link
Owner

I am aware of the weaknesses of the "database." I am looking at possibly having settings/snowflake/other stats stored remotely and acquired when a player logs in.

@ghost
Copy link

ghost commented Mar 1, 2015

@twizmwazin like remote DB?

@twizmwazin
Copy link
Owner

@RubeGamerV perhaps

@afeham
Copy link

afeham commented Mar 23, 2016

Is this being worked on?

@Pablete1234
Copy link
Collaborator

@intenseoxygen more like the other way arround, database is now needed for ranks to work (in cardinal 1.9), moved all the data for who has what ranks to there, instead of the config-based saving that we had before

@afeham
Copy link

afeham commented Mar 23, 2016

@Pablete1234 nice keep it up

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants