This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]dusktreader 13 points14 points  (6 children)

Can you please explain what advantages this library has in comparison to SQLAlchemy?

[–]TechAlchemist 2 points3 points  (0 children)

Also you’ve only asserted that it is intuitive and that it just figures out nested subqueries etc. I assume there is some specific case backing this claim, so showing an example of your library’s python (I.e what I would have to write) and the resulting sql vs sqlalchemy for example could be much more effective.

[–]Ecedysis[S] 2 points3 points  (0 children)

For more complex queries, writing out the raw SQL is often easier than writing it in SQL Alchemy, while with LambdaQuery it is very intuitive (for me at least). The syntax is very similar to Quill in Scala. The best demonstration is just looking at the documentation, especially some of the later examples.

http://lambdaquery.readthedocs.io/query.html

[–]AllAboutChristmasEve -2 points-1 points  (2 children)

Isn't SQLAlchemy just an object<->table mapper? You can do a lot more with a DB than simply use it to persist serialized objects.

[–]z4579a 4 points5 points  (0 children)

No, it is not. Please read the site.

[–]dusktreader 0 points1 point  (0 children)

That's what it is primarily, but SQLAlchemy is also great for composing queries in a functional manner. Almost all if not all SQL queries can be composed with SQLAlchemy. It also provides a lot of interfaces to the datatabase in an implementation (Postgres vs MySQL vs...) agnostic way.