Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Database dependent data may not be kept separate with regard to different database files #26

Open
jnharton opened this issue Oct 17, 2013 · 0 comments
Assignees
Labels

Comments

@jnharton
Copy link
Owner

jnharton commented Oct 17, 2013

Basically, the code can be told to use a different database, but any other data which is dependent on a database is not necessarily kept separate.

The internal game mail is one such piece of data.

I happened to have two database files, DB1 and DB2 respectively, then user 'admin' on DB1 would have access to the mail of any user 'admin' and vice versa. I.e. no matter how many databases I use there is only one mail file for user 'admin'. The first one will be a new mail file and thereafter all other admins will get that, barring creating a new character with that name.

Consequently, that file might get overwritten if another DB is used and a new character is created with the same name as an existing character in another one.

Obviously this is something that ought to be dealt with, because it's really dumb.

@jnharton jnharton added this to the Clean Up Current Issues milestone Mar 4, 2021
@jnharton jnharton changed the title Database dependent data not enclosed/encapsulated with regard to database Database dependent data may not be kept separate with regard to different database files May 14, 2024
@jnharton jnharton self-assigned this May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant