Were I interested in writing a loosely coupled storage engine for
MySQL/MariaDB I like the API and docs available for PG and SQLite. We don't
have docs like that and the API was much more difficult back in the day
when I supported something that did this:
On 08/19/2013 07:43 PM, MARK CALLAGHAN wrote:
Welcome back to the MySQL community Jan. It is good to see
SkySQL/MariaDB get more InnoDB expertise.
Thanks, I have really enjoyed back on MySQL community. Many things are
changed but many are as they were when I was moved to develop other
Thanks for your response.
On Fri, Aug 16, 2013 at 11:23 AM, Zardosht Kasheff zardo...@gmail.comwrote:
I've worked on the TokuDB storage engine for quite a while now. I have
had many experiences over the years, so I guess it's hard to know
where to begin. I guess I will start small, and if the
Hi,
From experience working on two storage engines on MySQL and being main
developer for the second one, and one storage engine on big company, I
would say MySQL storage engine API has some legacy problems and clearly
some missing functionality. e.g.
- Some part of the storage engines are
Welcome back to the MySQL community Jan. It is good to see SkySQL/MariaDB
get more InnoDB expertise.
On Mon, Aug 19, 2013 at 9:32 AM, Jan Lindström jplin...@mariadb.org wrote:
Hi,
From experience working on two storage engines on MySQL and being main
developer for the second one, and one
I think PBXT is the best example till now that the SE API actually works.
Paul, who created it, also was not grown in MySQL but he managed to figure
out good enough to write a complete transactional general-purpose storage
engine.
It did not quite reach GA level. But I don't think the API is to
Hi Mark,
TokuMX is a quite different beast than TokuDB. First of all, we already
had the experience of integrating our engine into one database product
before we started. So many kinks in the TokuKV layer had already been
worked out.
But more importantly, TokuMX/MongoDB doesn't have a storage
Hi, Zardosht!
Thanks for your feedback!
I'm looking at the storage engine API from the other side, but my
opinion is mostly the same as yours.
Current API works, but it could be simplified/clarified in few places.
There are part of it that I needed to explain many times. And I was
saying,
The storage engine API has never been my favorite part of MySQL. I haven't
written a storage engine but I used to maintain a custom storage engine and
migrated that from 4.0 to 5.0 so I had some experience with the API.
Is there a different API that would make it easier for innovation to come
to
9 matches
Mail list logo
