SQLAlchemy is… an acquired taste, but it’s very popular, and because it’s so popular I am absolutely certain that my distaste for SQLAlchemy is because I’m too stupid to understand it**, so we’re going to use it for this example.
Peewee is one that’s pretty simple to get running with, but it isn’t as popular as SQLAlchemy. There are a handful of ORMs that work for Python, and plenty that work with Flask. ORM means Object-relational mapping, which doesn’t mean anything to anyone and no one will ever ask you about that So the Gods invented ORMs, which basically mean “instead of writing SQL you’ll just write Python and the ORM will talk to the database for you.” Then everyone else was invented, and they didn’t like writing SQL, they just liked writing Python. Once upon a time there were databases, and there was SQL, and there were people who loved writing SQL.
That’s a fate worse than ten or twenty unimaginable terrors. Return dict((scription, value)ĭear Reader, my Sweet Friend, that’s horrible. Oof, eef, aaf, this “simple example” it hurts parts of my body I didn’t even know I had.Īnd then under the header “Easy Querying” it shows you this real baller piece of work: def make_dicts(cursor, row): Brace yourself and take a look at this awesome “simple example of how you can use SQLite 3 with Flask” DATABASE = '/path/to/database.db' def get_db():ĭb = g._database = sqlite3. If you’ve used things like sqlite3 or pg8000 to talk to databases before, you know it can really be a pain to wrangle your data. 6.1.1 Cleaning text in our Jinja2 templates.6 Leveling up with advanced SQLAlchemy queries.5.6 Linking from the index to the detail page.5.3 Sending meaningful data to the template.1.3 Why in the name of undiscovered species am I doing this?.
0 kommentar(er)
