[Maria-developers] Learning Storage Engine API
Dear all, This question is directed to Sergei Golubchik at Monty Program, although input from anyone's experience would be valuable. What is the best approach, in your opinion, to start learning storage engine API? So that one can write a dummy storage engine in no time. Igor Kozachenko University of California, Berkeley
Hi Igor On 19/04/2010, at 1:01 PM, Igor K wrote:
This question is directed to Sergei Golubchik at Monty Program, although input from anyone's experience would be valuable.
It can be helpful to look at an existing engine with simple design, like CSV (Tina engine) or Federated(x). Cheers, Arjen. -- Arjen Lentz, Exec.Director @ Open Query (http://openquery.com) Exceptional Services for MySQL at a fixed budget. Follow our blog at http://openquery.com/blog/ OurDelta: packages for MySQL and MariaDB @ http://ourdelta.org
On Mon, 19 Apr 2010 13:01:19 -0700, Igor K <igor175@gmail.com> wrote:
This question is directed to Sergei Golubchik at Monty Program, although input from anyone's experience would be valuable.
What is the best approach, in your opinion, to start learning storage engine API? So that one can write a dummy storage engine in no time.
As this question has come up on the Drizzle lists as well. There are some bits that are rather different between the MySQL/MariaDB API and Drizzle API. The table discovery bit is totally different. Check out ARCHIVE for an example in MySQL/MariaDB (and also for Drizzle a bit, but check out embedded_innodb in Drizzle for a more complete implementation). DDL is also different. Again, check embedded_innodb for Drizzle. The InnoDB example may be useful for MySQL, but I'm not all that sure... I'd suggest NDB, but that has its own added complexity... For basic DML, you can check out CSV for probably the most basic yet functional implementation. -- Stewart Smith
participants (3)
-
Arjen Lentz
-
Igor K
-
Stewart Smith