Time |
Nick |
Message |
00:14 |
Zughy[m] |
Do I smell possible close after the latest comment? #13266 |
00:14 |
ShadowBot |
https://github.com/minetest/minetest/issues/13266 -- MariaDB Database Backend by caffeinatedblocks |
00:26 |
|
ShadowBot joined #minetest-dev |
03:32 |
|
ivanbu joined #minetest-dev |
03:53 |
|
v-rob joined #minetest-dev |
04:00 |
|
MTDiscord joined #minetest-dev |
04:25 |
|
calcul0n joined #minetest-dev |
04:31 |
|
diceLibrarian joined #minetest-dev |
04:48 |
|
v-rob joined #minetest-dev |
05:22 |
|
tekakutli joined #minetest-dev |
06:06 |
|
tekakutli joined #minetest-dev |
06:10 |
|
YuGiOhJCJ joined #minetest-dev |
07:00 |
|
appguru joined #minetest-dev |
07:14 |
|
imi joined #minetest-dev |
07:18 |
imi |
appguru: I haven't heard regarding my PR https://github.com/minetest/minetest_game/pull/3030 since a while. Is it accepted? Do I need to still work on it? |
08:58 |
|
YuGiOhJCJ joined #minetest-dev |
09:01 |
pgimeno |
Zughy[m]: I don't think his comment applies to this backend, so no. |
09:06 |
pgimeno |
These comments apply to an SQL-based application with queries distributed all along the app. I've been there, having to switch the engine once, and he's right in that case. But Minetest database drivers are database-specific and self-contained, and there are no SQL queries anywhere else, so his comments about the differences between the different backends do not apply to this case. |
09:10 |
pgimeno |
As for his other argument that the environments that allow minetest to run also allow you to install other database backends, that's true, but if you already have an installation with MySQL, having to install and learn another database backend when you already have one is a burden, for you and for the server. |
09:23 |
|
kuroya joined #minetest-dev |
10:58 |
|
Noisytoot joined #minetest-dev |
11:00 |
|
appguru joined #minetest-dev |
11:03 |
rubenwardy |
Yeah, the fact the backend is contained means there's not much architectural risk. It would just be maintenance risk |
11:04 |
rubenwardy |
I'm not going to review that PR, I don't think it would be a good use of my time. Would rather work on polishing up the settings GUI |
11:07 |
rubenwardy |
if you support a PR, you should at least plan to review it. Looks like nrz, lhofhansl, and x2048 are the supporters here |
11:07 |
sfan5 |
I'll probably review it .. some time |
11:07 |
rubenwardy |
haha |
11:07 |
rubenwardy |
not saying they don't plan to review it |
11:28 |
Zughy[m] |
I still don't understand why we should support something that requires more maintenance than the one we already provide |
11:33 |
|
Warr1024 joined #minetest-dev |
11:35 |
MTDiscord |
<Troodon> Look I found 😊 enjoy  https://discord.gg/cg3VBQBnuq  @everyone @here |
11:35 |
ROllerozxa |
er... you probably shouldn't click on that link |
11:35 |
rubenwardy |
(scam link) |
12:06 |
|
Noisytoot joined #minetest-dev |
12:25 |
|
Noisytoot joined #minetest-dev |
12:59 |
MTDiscord |
<Thresher> what scam link? |
13:06 |
|
appguru joined #minetest-dev |
14:13 |
|
Desour joined #minetest-dev |
17:15 |
|
Andreas[m]1 joined #minetest-dev |
17:39 |
|
appguru joined #minetest-dev |
20:39 |
|
appguru joined #minetest-dev |
21:15 |
|
v-rob joined #minetest-dev |
22:08 |
|
v-rob joined #minetest-dev |
22:32 |
|
panwolfram joined #minetest-dev |
22:59 |
|
Desour joined #minetest-dev |
23:10 |
|
AliasAlreadyTake joined #minetest-dev |
23:54 |
|
YuGiOhJCJ joined #minetest-dev |