Why is PrepareStatement protected?

[crowbait]

The PrepareStatement method on MySQLConnection is protected.
I was wondering why - being able to prepare one's own statements would enable module authors to improve database performance. As it stands, the options are to either use unprepared statements or to modify the core source to have custom prepared statements to use.
Neither is ideal.

[Nyeriah]

Converted to discussion as its not an issue/bug

[UndeadRogue]

This is exactly where I got stuck too and was surprised at this limitation given how otherwise flexible the module system is.

It's also currently impossible (though someone better than me at C++ might be able to prove me wrong) to create a custom database worker pool because it uses templates and the linker always fails if you try.

Case in point: Playerbots has to modify the core in order to use its own schema/prepared statements. It's definitely a limitation that doesn't seem necessary

[UndeadRogue]

my solution: #24525 for comment