Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-12-08 Thread Jens Rehsack
Am 13.11.2014 um 17:18 schrieb Jens Rehsack rehs...@cpan.org: Am 13.11.2014 um 16:47 schrieb Peter Rabbitson rab...@rabbit.us: On 11/13/2014 04:07 PM, Jens Rehsack wrote: ... political correctness guards (sorry, I do not see any advantage in the don't ever do this because it's

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-13 Thread Tim Bunce
My impression was that there was a risk of breaking existing users apps. If that can be avoided then great, and keeping the name would be best. Tim. On Thu, Nov 13, 2014 at 07:12:33AM +0100, Jens Rehsack wrote: Am 12.11.2014 um 16:14 schrieb Tim Bunce tim.bu...@pobox.com: Perhaps the

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-13 Thread Jens Rehsack
Am 13.11.2014 um 14:37 schrieb Tim Bunce tim.bu...@pobox.com: My impression was that there was a risk of breaking existing users apps. If that can be avoided then great, and keeping the name would be best. Neither, nor :( They're already broken. The intension is, to pick them up and lead

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-13 Thread H.Merijn Brand
On Thu, 13 Nov 2014 14:58:55 +0100, Jens Rehsack rehs...@cpan.org wrote: Am 13.11.2014 um 14:37 schrieb Tim Bunce tim.bu...@pobox.com: My impression was that there was a risk of breaking existing users apps. If that can be avoided then great, and keeping the name would be best.

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-13 Thread Peter Rabbitson
On 11/13/2014 07:12 AM, Jens Rehsack wrote: Reason to keep: People continuous ask me about AnyData / DBD::AnyData and send me fiddly patches hacking in the module, complain about working around compat issues etc. So what I currently know: every AnyData / DBD::AnyData user makes adoptions to

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-13 Thread Jens Rehsack
Am 13.11.2014 um 15:08 schrieb Peter Rabbitson rab...@rabbit.us: On 11/13/2014 07:12 AM, Jens Rehsack wrote: Reason to keep: People continuous ask me about AnyData / DBD::AnyData and send me fiddly patches hacking in the module, complain about working around compat issues etc. So what I

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-13 Thread Peter Rabbitson
On 11/13/2014 04:07 PM, Jens Rehsack wrote: ... political correctness guards (sorry, I do not see any advantage in the don't ever do this because it's forbidden in general). You need to clarify what you mean, language seems to be getting in the way. What do you perceive as political

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-13 Thread Jens Rehsack
Am 13.11.2014 um 16:47 schrieb Peter Rabbitson rab...@rabbit.us: On 11/13/2014 04:07 PM, Jens Rehsack wrote: ... political correctness guards (sorry, I do not see any advantage in the don't ever do this because it's forbidden in general). You need to clarify what you mean, language

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-12 Thread Tim Bunce
Perhaps the module name should be changed. Tim. On Wed, Nov 12, 2014 at 10:33:20AM +0100, Jens Rehsack wrote: Hi, for a recent project we identified DBD::AnyData as best concept to do a client's job ;) So there is a tuit to do the groundwork for bringing AnyData back to modern DBI

Re: Bring AnyData / DBD::AnyData back to work with modern DBI

2014-11-12 Thread Jens Rehsack
Am 12.11.2014 um 16:14 schrieb Tim Bunce tim.bu...@pobox.com: Perhaps the module name should be changed. Why? Let me just talk about the reason to keep and the consequence to change. Reason to keep: People continuous ask me about AnyData / DBD::AnyData and send me fiddly patches hacking in