maria-discuss team mailing list archive

[Tanstaafl <tanstaafl@xxxxxxxxxxxxxxx>]

Well, I guess I should expect no less from you Reindl... occasionally 
you're helpful, but more often than not you simply ignore very specific 
questions like the one in this email) and just have to flex your 
superiority complex.

On 6/30/2014 8:01 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
> Am 30.06.2014 13:59, schrieb Tanstaafl:
> > Reindl/anyone?
>
> comlain at the client developers
>
> what else
>
> nobody else has such problems
> you even state before update the client there was no problem
> if you update software B and things break why seek the
> problem in software A at all?
>
> > On 6/22/2014 12:01 PM, Tanstaafl <tanstaafl@xxxxxxxxxxxxxxx> wrote:
> > > On 6/19/2014 7:34 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
> > > > Am 19.06.2014 13:17, schrieb Tanstaafl:
> > > > > On 6/18/2014 7:53 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
> > > > > > the client seems to use the very outdated mysql4 protocol
> > > > > > which is not compatible
> >
> > > > > When you say 'not compatible' - do you mean that mariadb simply will
> > > > > (would) not work with that protocol if the software attempts to use it?
> >
> > > > that's not a matter of MariaDB
> > > > it's a matter that MySQL4 passed away nearly 10 years
> >
> > > So, just to be clear...
> > >
> > > What should this be saying? Something like:
> > >
> > > "... ERROR: could not open MySQL5 connection to database..." ?
> > >
> > > In other words, should the mysql4 be mysql5?
> > >
> > > Still trying to figure out a way to adjust logging to better assist
> > > troubleshooting this.
> > >
> > > I agree this is most likely a client (SOGo) problem since it only
> > > appeared after the last update, but the devs say otherwise (or mostly
> > > just remained silent)... so I'd like some additional ammunition before
> > > going back to them and opening up a bug...