Re^2: mysql_auto_reconnect and utf8

Hi

But documentation says that 'mysql_enable_utf8':
'This option is experimental and may change in future versions.'

So it safe to use?

Neid

Comment on Re^2: mysql_auto_reconnect and utf8

Replies are listed 'Best First'.
Re^3: mysql_auto_reconnect and utf8 by Joost (Canon) on Jan 27, 2008 at 22:38 UTC
Let's just say that not using it will cause more trouble than it's worth, and that if the option should eventually disappear or change it shouldn't be much work to change your code to adapt. Database drivers don't update themselves; just check when you install a new version. You should assume that all code using utf-8 with DBD::mysql on current versions will work better when that option is used. I'm using it in a couple of fairly large systems and the only real issue I've had is that it's not complete - you still have to make sure data specified for UTF-8 columns is really utf-8 before sending queries. Since 4.004 using the option will as far as I know at least guarantee you'll get your data back with correct status for the utf-8 marker of each column, for every type of column. Nothing else will give you that guarantee. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]

Replies are listed 'Best First'.

Re^3: mysql_auto_reconnect and utf8
by Joost (Canon) on Jan 27, 2008 at 22:38 UTC

not

You should assume that all code using utf-8 with DBD::mysql on current versions will work better when that option is used. I'm using it in a couple of fairly large systems and the only real issue I've had is that it's not complete - you still have to make sure data specified for UTF-8 columns is really utf-8 before sending queries.

Since 4.004 using the option will as far as I know at least guarantee you'll get your data back with correct status for the utf-8 marker of each column, for every type of column. Nothing else will give you that guarantee.

"What should it profit a man, if he should win a flame war, yet lose his cool?"

[reply]