Antipattern orisnull: the Cunning of Illusory Simplicity
summary
The talk analyzes the "or :param is null" SQL antipattern used for dynamic filters (e.g., where user.name = :name or :name is null), showing how that convenient pattern causes hard-to-see performance problems even with ORMs like Hibernate or Spring Data. It explains why these queries tend to proliferate across projects and describes using code generation to eliminate or minimize the performance damage they cause.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:35Talk overview
- 5:23OR NULL in SQL queries
- 15:57Frameworks and ORM role
- 21:36Alternative solutions
- 29:05Custom solution design
- 44:56Results and summary
- 49:14Q&A
related talks
36mORM is an Offensive Anti-Pattern
48mORM Iinsights - How to Not Hurt Yourself?
44mORM Insights - How not to hurt yourself?
47mWhen ORM Becomes OMG: Performance Pitfalls in JPA and Friends
35mThe League of Extraordinary Antipattern
52mThe SQL inside the ORM/Builder box | Claudio Zizza
46mJimmer ORM: An Alternative to JPA
58mCause of Death: Hibernate.