Taking Aim At The Legacy Of SQL With The Preql Relational Language
July 27th, 2021
36 mins 38 secs
About this Episode
SQL has gone through many cycles of popularity and disfavor. Despite its longevity it is objectively challenging to work with in a collaborative and composable manner. In order to address these shortcomings and build a new interface for your database oriented workloads Erez Shinan created Preql. It is based on the same relational algebra that inspired SQL, but brings in more robust computer science principles to make it more manageable as you scale in complexity. In this episode he shares his motivation for creating the Preql project, how he has used Python to develop a new language for interacting with database engines, and the challenges of taking on the legacy of SQL as an individual.
- Hello and welcome to Podcast.__init__, the podcast about Python’s role in data and science.
- When you’re ready to launch your next app or want to try a project you hear about on the show, you’ll need somewhere to deploy it, so take a look at our friends over at Linode. With the launch of their managed Kubernetes platform it’s easy to get started with the next generation of deployment and scaling, powered by the battle tested Linode platform, including simple pricing, node balancers, 40Gbit networking, dedicated CPU and GPU instances, and worldwide data centers. Go to pythonpodcast.com/linode and get a $100 credit to try out a Kubernetes cluster of your own. And don’t forget to thank them for their continued support of this show!
- Your host as usual is Tobias Macey and today I’m interviewing Erez Shinan about Preql, an interpreted, relational programming language, that specializes in database queries
- How did you get introduced to Python?
- Can you describe what Preql is and the story behind it?
- What are goals and target use cases for the project?
- There have been numerous projects that aim to make SQL more maintainable and composable. What is it about the language and syntax that makes it so challenging?
- How does Preql approach this problem that is different from other efforts? (e.g. ORMs, dbt-style Jinja, PyPika)
- How did you approach the design of the syntax to make it familiar to people who know SQL?
- Can you describe how Preql is implemented?
- How has the design and architecture changed or evolved since you began working on it?
- What is a typical workflow for someone using Preql to build a library of analytical queries?
- Beyond strict compilation to SQL, what are some of the other features that you have incorporated into Preql?
- How does a Preql program get executed against a target database, particularly when using capabilities that can’t be directly translated to SQL?
- ** What are the main difficulties / challenges of compiling to SQL ?
- What are some of the features or use cases that are not immediately obvious or prone to be overlooked that you think are worth mentioning?
- What are the most interesting, innovative, or unexpected ways that you have seen Preql used?
- What are the most interesting, unexpected, or challenging lessons that you have learned while working on Preql?
- When is Preql the wrong choice?
- What do you have planned for the future of Preql?
Keep In Touch
- Thank you for listening! Don’t forget to check out our other show, the Data Engineering Podcast for the latest on modern data management.
- Visit the site to subscribe to the show, sign up for the mailing list, and read the show notes.
- If you’ve learned something or tried out a project from the show then tell us about it! Email firstname.lastname@example.org) with your story.
- To help other people find the show please leave a review on iTunes and tell your friends and co-workers
- Join the community in the new Zulip chat workspace at pythonpodcast.com/chat
- Relational Algebra
- ORM == Object Relational Mapper
- Rich terminal UI library
The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra / CC BY-SA