All, looks like my first message on this never reached the list, so
sending again.
I've prepped the release notes and changelog pages for this release and
will be activating it in a few hours (barring any show stoppers).
- https://kb.askmonty.org/en/mariadb-galera-5528a-release-notes/
- https
Hi, Sanja!
On Dec 21, sa...@askmonty.org wrote:
> At file:///home/bell/maria/bzr/work-maria-10.0-cassandra/
>
> revno: 3484
> revision-id: sa...@askmonty.org-20121221010609-cnr2z3fg99kpxzma
> committer: sa...@askmonty.org
> branch nick:
Hi,
I recently switched from MySQL 5.6.5 to MariaDB 10.0,
and I've been seeing errors like the following in the
logs since:
121221 13:22:34 [ERROR] Master 'master1': Found index PRIMARY whose
column info does not match that of MySQL.
121221 13:22:34 [ERROR] Master 'master1': Build InnoDB index
Hi,
> "madyncol" looks silly :)
> let's agree on one namespace prefix and use it everywhere. either it's
> ma_ like in
>
> ma_open
> ma_dyncol_create_many
> ma_alloc
>
> or it's maria_ like in
>
> maria_open
> maria_dyncol_create_many
> maria_alloc
I think we should use the vendor pre
Hi, Sanja!
On Dec 21, sa...@askmonty.org wrote:
> At file:///home/bell/maria/bzr/work-maria-10.0-cassandra/
>
>
> revno: 3482
> revision-id: sa...@askmonty.org-20121220233538-b171yhb9isogvd5h
> parent: sa...@askmonty.org-20121220204008-
Hi, Oleksandr!
On Dec 21, Oleksandr Byelkin wrote:
> It looks like you reviewed some old sources in 10.0-cassandra this is
> fixed as we discussed it.
I've reviewed the 5.5-cassandra tree. And yes, I thought that was
already fixed, so I was a bit susprised to find it unfixed :)
Ok, wrong tree,
6 matches
Mail list logo
