On 2017-11-10 5:58 PM, Dan Book wrote:
On Fri, Nov 10, 2017 at 8:43 PM, Noel Butler wrote:
Given that things are only ever going to move forward with my/maria-sql
would it not be better to enable this by default, and have a "disable"
setting for those who want to run something of antiques?
Because in years to come there will only ever be the modern versions and
you;ll have to change default behaviour then anyway, but since that time is
mostly here now, it makes more sense to enable it by default.
No, this whole issue came about because existing code requires modification to
continue working. Requiring a new option to be set to enable old behavior would
cause the same problem. Backcompat is "forever".
Yes, exactly.
However, other things we CAN do include:
1. Prominently document the new switch with the strong recommendation that
people flip it on by default in new code just as part of good housekeeping.
Basically in the same vein as recommending use-strict or use-warnings without
turning them on by default. This also means that all code examples for
DBD::mysql should make sure to include setting the flag on.
2. After a reasonable but relatively short delay following the first version
with this switch, make DBD::mysql issue warnings when it is used without turning
that switch on. That should draw the attention of people that they need to
update their code to work more properly but without actually breaking anything
(unless someone uses warnings with FATAL, but then they asked for it). I say
have a delay so that people who pay attention and would fix their code soon
don't have reams of warnings appearing in their server logs. Although in
general to keep the warning count down it could probably just be issued the
first time a connection handle is used without the flag.
3. Make sure that at least the public or known Perl code using DBD::mysql and
has reasonable control over use of the handle would turn the flag on.
So Darkpan is mainly handled by #1 and #2 such as it can be.
-- Darren Duncan
