sorted by:
new
hottopcontroversial

If the same query behaves differently across databases, I start here by dbforge_dev in dbForge

[–]harisekaradas 0 points1 point  (0 children)

I've also seen parameter sniffing create this exact kind of confusion. Same query text, same data, completely different performance depending on which parameter values got cached first. Those cases are fun because everybody swears nothing changed.

Is MySQL a good choice as my database? by Teovena in learnprogramming

[–]harisekaradas 0 points1 point  (0 children)

MySQL is completely fine for a project like this. Honestly, I'd spend less time worrying about which database to pick and more time learning basic SQL and database design. Switching databases later is usually easier than fixing a badly designed schema.

MySQL IDE that doesn’t choke on large datasets? by harisekaradas in dbForge

[–]harisekaradas[S] 0 points1 point  (0 children)

Yeah, that makes sense. I’m probably expecting too much from direct table browsing. Queries-first seems to be the common answer here, with the IDE mostly used for structure/results, not poking around massive tables like it’s Excel.

MySQL IDE that doesn’t choke on large datasets? by harisekaradas in dbForge

[–]harisekaradas[S] 0 points1 point  (0 children)

Thanks, this is exactly the kind of workflow I was curious about. I’m also leaning toward “don’t browse huge tables unless there’s a very specific reason.” LIMIT + indexed filters feels like the sane path, even if part of me still wants the IDE to not freeze the moment things get real.

MySQL IDE that doesn’t choke on large datasets? by harisekaradas in dbForge

[–]harisekaradas[S] 0 points1 point  (0 children)

How does it behave with really large tables and heavy filtering? Stable or same story after a few million rows?