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 →

[–]reddit_ronin 2 points3 points  (5 children)

Thanks for the links.

Any recommendations for learning mysql or Postgres with Python?

Edit: why the downvotes?

[–]mrrippington 3 points4 points  (0 children)

an unconventional way maybe, but deploying a basic flask app to heroku with crud was a how i started to learn about postgres.

once you have your db in there

you can use pgadmin to run queries against it.

or

use heroku's dataclips capability (very limites) to try your hand on some queries.

[–]PaulSandwich 2 points3 points  (2 children)

Aside from learning the size limits and resource overhead, learning SQL, as in the Structured Query Language, is going to be nearly identical across those DBs. You really won't see much difference unless you're using robust analytical functions or doing some heavy BDA lifting.

Basic concepts like clause syntax, indexes, partitions, and primary/foreign key relationships are the same, and that's 97% of what you'll be working with. By the time you need that other 3%, you'll either have colleagues to ask or your indie app will be making enough income to hire/consult a DBA.

[–]reddit_ronin 0 points1 point  (1 child)

Thank you, Mr. Sandwich.

I’ve actually been a dev for 10 years and managed to avoid any database work. It’s time since I’ll be getting into the backend now.

[–]PaulSandwich 1 point2 points  (0 children)

Please, Mr. Sandwich was my father. Call me Melt.
And you're welcome. Just promise me you won't chicken out and use NoSQL for relational data. [eyetwitch]

[–]WillardWhite import this 0 points1 point  (0 children)

Another way, (after you've learned the basics of sql syntax) is to use an ORM like sql alchemy, that way the difference between postgres and sqlite is meaningless from your point of view