thorn idol
Hey y'all! I'm hoping someone smarter than me can fill a gap in my understanding of Pterodactyl. What is the point of making databases when you start your game server? I see a lot of hosting providers advertise it as one of their features too. Does it benefit the players in certain situations?
Thanks!
hearty kestrel
Some game or plugins of games needs databases. And somethimes you have more then 1 plugin that needs its own database.
thorn idol
Some game or plugins of games needs databases. And somethimes you have more then...
oh okay interesting! Yeah I've never really been into plugins so that's news to me. Thanks!
robust axle
Some game or plugins of games needs databases. And somethimes you have more then...
Different tables exist for that reason.
hearty kestrel
Different tables exist for that reason.
they do ofc but it is just there if people want it
robust axle
oh okay interesting! Yeah I've never really been into plugins so that's news to ...
One database is enough, you can just create multiple tables within that database
robust axle
they do ofc but it is just there if people want it
I guess. It is just a bit impractical, because within the same database you can easily make relations etc, while if you use multiple databases it gets a bit more complicated.
random wolf
One database is enough, you can just create multiple tables within that database
not recommended really, one plugin messes up and you loose everything connected to it
robust axle
not recommended really, one plugin messes up and you loose everything connected ...
For relations between tables one database would be key.
robust axle
not recommended really, one plugin messes up and you loose everything connected ...
If one plugin messes up one table you can just reset that table or correct it.
Unless you assume that a plugin could wipe an entire database. (Accidentally or otherwise)
robust axle
Unless you assume that a plugin could wipe an entire database. (Accidentally or ...
In this case I would agree with your statement.
barren lynx
Plenty of plugins have table names that would overlap. Far more reasonable to use separate databases for each plugin.
Trying to use one database for a whole bunch of unrelated things is just asking for trouble
random wolf
If one plugin messes up one table you can just reset that table or correct it.
plugins can accidently mess the entire database up
how would a plugin with malicious intent be accidentally
random wolf
Trying to use one database for a whole bunch of unrelated things is just asking ...
^^
robust axle
how would a plugin with malicious intent be accidentally
My wording was a bit awful on that one
robust axle
^^
“Unless you assume that a plugin could wipe an entire database. (Accidentally or otherwise)”
That is what I meant with it
robust axle
Trying to use one database for a whole bunch of unrelated things is just asking ...
I guess I am just used to using only one database with a lot of tables due to web development. (Per website)
barren lynx
That's totally different tho. That's one application, and you have control over the development of the schema or at least table prefixes.
robust axle
That's totally different tho. That's one application, and you have control over ...
Yes it is different, I went at it with that approach. This conversation has adjusted my views on this topic and I will implement something for it accordingly.
random wolf
👍