- 01 Nov 2016 15:00
Hiroku wrote:By the built-in, you're referring to the Pixelmon2.h2? Or the save-data database? Built-in implies the former but your use-case sounds like the latter.
If you mean the Pixelmon2 then I wouldn't understand the point, for any number of reasons. Slow, no benefit, etc.
What I assume you mean is the custom database for player Pokémon data. In that case, converting an existing one that's H2 Embedded over to MySQL wouldn't be too big a deal because the two have similar complexity. The creation of the columns doesn't actually differentiate between H2 and MySQL, so there's no issue of incompatible types; you're in the clear there. A dump should be accepted into the other DBMS without much issue. Though I didn't know the database code worked well enough to use on a larger scale so props to you for getting by with it.
Hey, thanks for the response.
I was originally talking about the Pixelmonh2 db as I had misunderstood (misread) what the configuration setting for an external database actually does (mind you, it is very clear in the config, just my mistake there.)
As to why? Well, without knowing anything about the inner-workings of the mod I already have a dedicated MySQL backend on beefier hardware that is the ultimate solution-needing-a-problem, which is where a lot of this stems from I think, ha. A part of it might have just been the fact that I work in an environment where offloading SQL is assumed, though it should be said that that is a series of incredibly different use-cases than what we are talking about here, in which case something like H2 I'm sure is a very good choice.
What I do mean now, yes, is (was) dumping out whatever is holding the existing (default location) playerdata to get that bad boy into MySQL. I don't think I'm likely to pursue it now, though, as there wouldn't be much of a benefit with the tiny amount of data it would be storing and the low number of players this server will ever likely see.
At any rate, thanks again for the timely and informative response!