Update DB Structure #57

Rustypredator · 2019-05-05T13:17:47Z

Reference Issue: #49
The Changes make sure, that you do'nt have duplicate data in the Database by separating the Data, that changes from the data that is static.
That way you'll also save space (a little).

e.g. every player would only need to be created once. the Ping data will go into player_data
same with worlds.

ER-Diagramm:

I hope you'll be able to implement these changes, as it would make using the DB way easier.
I'm sorry it took so long, but i was really busy the past few months :)

if there are any questions i'll be happy to answer :)

Reference Issue: games647#49 The Changes make sure, that you do'nt have duplicate data in the Database by separating the Data, that changes from the data that is static. That way you'll also save space (a little). e.g. every player would only need to be created once. the Ping data will go into `player_data` same with worlds. if there are any questions i'll be happy to answer :)

Replaced `native_id` with `id`. It makes it easier to use the db, when you use the format `tablename.fieldname` e.g: `prefix_native.id` instead of `native.native_id`.

Rustypredator added 2 commits May 5, 2019 15:15

id

7f95956

Replaced `native_id` with `id`. It makes it easier to use the db, when you use the format `tablename.fieldname` e.g: `prefix_native.id` instead of `native.native_id`.

Base automatically changed from master to main January 20, 2021 08:41

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update DB Structure #57

Update DB Structure #57

Rustypredator commented May 5, 2019 •

edited

Loading

Update DB Structure #57

Are you sure you want to change the base?

Update DB Structure #57

Conversation

Rustypredator commented May 5, 2019 • edited Loading

Rustypredator commented May 5, 2019 •

edited

Loading