4 ms·
You can have functional SQL query languages that map directly to SQL without object oriented row mapping. Everyone can use these tools without performance issu
by zzzeek 9y ago
You can have functional SQL query languages that map directly to SQL
without object oriented row mapping. Everyone can use these tools without performance issues.
Disclaimer: i wrote SQLAlchemy.
- nerdponx 9y agoIs that really a disclaimer, or just the source for your claim? I'm sure you know this, but there are actually several "query builder" tools out there for Python, including SQLAlchemy Core. I'd love to see a side-by-side comparison.
- lobster_johnson 9y agoHe probably meant "disclosure", not "disclaimer".
- mshenfield 9y ago> You can have functional SQL query languages that map directly to SQL without object oriented row mapping. Well said. I always think of this as the canonical example: http://sqlkorma.com/ http://sqlkorma.com/ I don't know what rock I've been under, but didn't realize SQLAlchemy had the same idea w/ SQLAlchemy Core.
- Dangeranger 9y agoAnother excellent example of this is Elixir's Ecto library for composing SQL from modular fragments https://github.com/elixir-ecto/ecto/blob/master/README.md https://github.com/elixir-ecto/ecto/blob/master/README.md
- virtualwhys 9y ago> without object oriented row mapping Korma seems to do exactly that, N+1 lazy loaded queries included. SQLAlchemy, Esqueleto, Slick, Quill, and the like all generate precisely what you tell them to (i.e. queries semantically the same as what you'd write by hand). This is not to disparage Korma, it looks pretty cool, I'd certainly give it a look if I worked with Clojure.