Extending MySQL with VillageSQL
The article discusses the extensibility of MySQL through a new fork called VillageSQL. It highlights the author's experience in creating an extension for the Roaring Bitmap data structure. The author shares insights on the development process, including challenges faced and solutions implemented.
- ▪VillageSQL allows users to add custom extensions to MySQL, enhancing its functionality.
- ▪The author created an extension for the Roaring Bitmap data structure, utilizing a template repository provided by VillageSQL.
- ▪Challenges included SQL syntax errors and issues with data structure size, which were resolved during the development process.
Opening excerpt (first ~120 words) tap to expand
One of the things that made me fall head over heals for Neo4j so many years ago was just how extensible it was. If the database engineering team was busy rebuilding the clustering feature for the third time and didn’t have time to take care of my feature requests… I could just add them myself. Not to Neo4j directly, no that would have been a horrible mess. Instead I could add any feature I wanted as an “Unmanaged Extension”. Later on they became Cypher Stored Procedures, but it was basically the same thing. You had access to the top level Java API that dealt with Nodes and Edges. You could use the Traversal API that dealt with Paths….and if you were feeling extra spicy that day you could go down to the Storage API that dealt with Cursors over raw bytes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Max De Marzi.
Discussion
0 commentsMore from Max De Marzi
