Did you ever try to find the few missing rows in a table holding an extremely large time series? Or did you have to fight with somebody else’s weird database design—storing data in columns that should have been rows, or even multiple values per field? Ever wanted to use a prepared query for a variable-sized IN-predicate?
Some common problems like these are solved easily and efficiently using an auxiliary table containing nothing but a sequence. This session will show you how, with hands-on examples—but instead of manually filling our sequence tables and wasting disk storage (or RAM) and I/O resources, we’ll use the SeqEngine: A pluggable storage engine for MySQL 5.1 that creates our customized sequences on the fly.
The session mostly concentrates on the SQL-side to the problems. But as this tiny engine also serves well as a nice example of how to make use of MySQL’s pluggable storage engine API, there will be an associated BOF: We’ll be able to have a closer look behind the scenes there.
Beat Vontobel is the CTO at MeteoNews AG, a Swiss weather forecasting company, where he initiated the transition from MS SQL to MySQL and generally from closed to open source a few years ago. The company used most of the new features of MySQL 5.0 right from the start (and will do so with 5.1) and Beat Vontobel, an active member of the MySQL community and of the MySQL guilds, regularly blogged about this experience.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Sharon Cordesse at email@example.com
Download the MySQL Sponsor/Exhibitor Prospectus
For media-related inquiries, contact Maureen Jennings at firstname.lastname@example.org
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the MySQL Conference newsletter.
View a complete list of MySQL contacts.