▲ 447 ▼ Lemmy.world down, probably following the upgrade. A reminder to move to smaller instances for a better experience (files.catbox.moe) submitted 3 years ago* by Blaze@sopuli.xyz to c/fediverse@lemmy.ml 255 comments fedilink hide all child comments
[–] Zetaphor@zemmy.cc 19 points 3 years ago (3 children) A 2-line SQL TRIGGER removal takes about minutes to fix. Then go fix it and open a PR permalink fedilink source parent hideshow 3 child comments replies: [+] RoundSparrow@lemmy.ml -9 points 3 years ago (2 children) Then go fix it and open a PR Do you think I am the one who created the mistake or something? That I have access to the servers to install it? It's so odd to me that you respond this way, as if it was my coding mistake. It isn't even me who opened issue, that is GitHub "makotech222" - is that your answer to them? permalink fedilink source parent hideshow 2 child comments replies: [–] degrix@lemmy.hqueue.dev 18 points 3 years ago (1 child) I don’t believe they’re insinuating that you were the one that created the mistake. Rather, that you seem to be knowledgeable of the specific problem and may be the one most capable of fixing it. The two line fix may be obvious to you, but may not to the main Lemmy devs. Until phriskey got involved, a lot of db tuning was being avoided (they’re responsible for most of the big db improvements this version). permalink fedilink source parent hideshow 1 child comment replies: [–] RoundSparrow@lemmy.ml -1 points 3 years ago a lot of db tuning was being avoided and I did not understand or properly relate to that project culture. It had been that way for years and I should have "read the room" "go with the flow". permalink fedilink source parent
[+] RoundSparrow@lemmy.ml -9 points 3 years ago (2 children) Then go fix it and open a PR Do you think I am the one who created the mistake or something? That I have access to the servers to install it? It's so odd to me that you respond this way, as if it was my coding mistake. It isn't even me who opened issue, that is GitHub "makotech222" - is that your answer to them? permalink fedilink source parent hideshow 2 child comments replies: [–] degrix@lemmy.hqueue.dev 18 points 3 years ago (1 child) I don’t believe they’re insinuating that you were the one that created the mistake. Rather, that you seem to be knowledgeable of the specific problem and may be the one most capable of fixing it. The two line fix may be obvious to you, but may not to the main Lemmy devs. Until phriskey got involved, a lot of db tuning was being avoided (they’re responsible for most of the big db improvements this version). permalink fedilink source parent hideshow 1 child comment replies: [–] RoundSparrow@lemmy.ml -1 points 3 years ago a lot of db tuning was being avoided and I did not understand or properly relate to that project culture. It had been that way for years and I should have "read the room" "go with the flow". permalink fedilink source parent
[–] degrix@lemmy.hqueue.dev 18 points 3 years ago (1 child) I don’t believe they’re insinuating that you were the one that created the mistake. Rather, that you seem to be knowledgeable of the specific problem and may be the one most capable of fixing it. The two line fix may be obvious to you, but may not to the main Lemmy devs. Until phriskey got involved, a lot of db tuning was being avoided (they’re responsible for most of the big db improvements this version). permalink fedilink source parent hideshow 1 child comment replies: [–] RoundSparrow@lemmy.ml -1 points 3 years ago a lot of db tuning was being avoided and I did not understand or properly relate to that project culture. It had been that way for years and I should have "read the room" "go with the flow". permalink fedilink source parent
[–] RoundSparrow@lemmy.ml -1 points 3 years ago a lot of db tuning was being avoided and I did not understand or properly relate to that project culture. It had been that way for years and I should have "read the room" "go with the flow". permalink fedilink source parent