Skip to content

Why use an ORM when you can just use straight up SQL in Python?

License

Notifications You must be signed in to change notification settings

tipsybear/ormbad

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ORMBad

Build Status Coverage Status Stories in Ready

Cleaning up Waders mess

Why use an ORM when you can just use straight up SQL in Python?

About

Object Relational Mappers (ORMs) seem like very useful tools, but unfortunately they can be tricky. Authors like @codinghorror and @martinfowler have given ORMs the fair shake in Object-Relational Mapping is the Vietnam of Computer Science and OrmHate (seriously, even with those titles). It seems like such a good idea, but adding them to your programs is not trivial.

The thing is, SQL is a really great tool also. Once you learn SQL and know how to avoid SQL-Injection attacks, it turns out that using straight SQL via Python in a driver is a joy. The question should not be: how do we manage objects whose storage layer is a database? The question should be, how do we manage reusable SQL strings in our applications. Hence we set out to write this tool.

Attribution

The image used in this README, Cleaning up Waders mess by Kristina Alexanderson, is licensed under CC BY-NC-ND 2.0.

About

Why use an ORM when you can just use straight up SQL in Python?

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published