[Dbi-link-general] Linking with non-UTF8-capable MySQL ?

[Georges Martin]

On Tue, May 5, 2009 at 5:06 PM, David Fetter <david at fetter.org> wrote:

> That would explain it.  Given that 4.0 is already past its end of life
> <http://www.mysql.com/about/legal/lifecycle/>, is there any chance of
> upgrading to a supported version of MySQL?


Unfortunately, no...


> Thanks to Harrison Fisk for help on this over in
> irc://irc.freenode.net/mysql
>
> If some entity decides to pay me a large hunk of money to create and
> maintain legacy compatibility code, I will be happy to support a
> version of MySQL so ancient that even its corporate owner has ended
> the last vestiges of support. :)
>

...as our application running atop MySQL 4.0 would be phased out in a 1-2
years timeframe. I think my boss will find our current export/import
procedure perfectly suitable until that... :-p

Anyway, thanks a lot for investigating the issue... :-)

One last thought: another database I'll link to is the underlying MS-SQL
of... hum... one of the market-leading ERP :-) There's about a thousand
tables but I need access to just a couple of these. Currently, DBI-Link
creates shadow tables and views for all the tables in the remote schema. Do
you have any plans to filter tables for DBI-Link 3.0 ? Do you think it would
be interesting to do it ?

Georges
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pgfoundry.org/pipermail/dbi-link-general/attachments/20090505/6d6ec2a8/attachment.html