Byrial Jensen wrote:
> I don't know if it is considered a bug that you cannot write
> const char *text = row;
The bug is in the construct, not in MySQL++. To make that work in
MySQL++, we'd have to return a pointer (or reference) to a static
object, and that opens up a whole new class of risks.
MySQL++ behaves reaonably in this regard. The question is how we make
people understand what the reasonable behavior is. :)
> but even if it isn't, it might be an idea to warn about the construction
> in the manual.
The only place an outright warning about this particular error will make
sense is in the reference manual, for Row's operator. But it might
also be good to have a general discussion of concepts in the userman.
Any ideas of where it should go, and how to approach it?