im just beginner to all of these .  i  just learning python and reached this point that there is sql and my sql and something called mango db i dont know which one to pick ? can i just learn 1 of them ? or i must take them all ?

 

 

Edited August 7, 20197 yr by sasa1000

any help 

Both databases are wildly different in how they work. One is a relational database, the other is more of a document store, often referred to as NoSQL. It really depends on what you intend to build.

Whatever you choose to learn don't do it via W3 Schools, that looks like the site you are on?  It's best avoided.

I'd agree with Jack and say learn things as you need them, you can't learn everything so if your app would be better served with a NoSQL database than learn one of those Note Mongo is one of those Dynamo is another that runs on AWS, there are various alternatives.
As there is with SQL based databases where you have Postgres MySQL etc etc.

On 8/12/2019 at 6:34 PM, Jack said:

Both databases are wildly different in how they work. One is a relational database, the other is more of a document store, often referred to as NoSQL. It really depends on what you intend to build.

for example build website for  articles and post comments on 

On 8/13/2019 at 11:23 AM, rbrtsmith said:

Whatever you choose to learn don't do it via W3 Schools, that looks like the site you are on?  It's best avoided.

I'd agree with Jack and say learn things as you need them, you can't learn everything so if your app would be better served with a NoSQL database than learn one of those Note Mongo is one of those Dynamo is another that runs on AWS, there are various alternatives.
As there is with SQL based databases where you have Postgres MySQL etc etc.

w3school is best  documentation i ever learnt from ? do u have alternative documents in order like it ?

1 hour ago, sasa1000 said:

for example build website for  articles and post comments on

Either will work if you want to build something like that, but I'd personally use something like MySQL because the data you're dealing with is relational. For example, you're relating comments to posts, and users to comments.

Edited August 14, 20197 yr by Jack
yolo

7 hours ago, Jack said:

Either will work if you want to build something like that, but I'd personally use something like MySQL because the data you're dealing with is relational. For example, you're relating comments to posts, and users to comments.

yes im gonna use python with  with sql and mysql  - 

so how i can    relate comments to posts, and users to comments ? via sql ? or mysql 

12 hours ago, sasa1000 said:

yes im gonna use python with  with sql and mysql  - 

so how i can    relate comments to posts, and users to comments ? via sql ? or mysql 

If that's the language you want to use, I would learn the Python fundamentals really well, then look into Django. You would be better off learning through proper tutorials rather than W3 Schools, the main Python tutorial I have heard of is https://learnpythonthehardway.org, I would look online for reviews of it.

In terms of how you would relate comments, it depends on the design of your system. You ideally need to understand how all of these pieces fit together first, database architecture being another topic entirely. On a simple level, you could have a comment table that stores the user ID, parent comment ID, and use those to relate users to comments.

A lot of what you're trying to do sounds like it could be achieved by using an existing blogging platform or CMS, so that might be something you want to look into first.

12 hours ago, Jack said:

If that's the language you want to use, I would learn the Python fundamentals really well, then look into Django. You would be better off learning through proper tutorials rather than W3 Schools, the main Python tutorial I have heard of is https://learnpythonthehardway.org, I would look online for reviews of it.

In terms of how you would relate comments, it depends on the design of your system. You ideally need to understand how all of these pieces fit together first, database architecture being another topic entirely. On a simple level, you could have a comment table that stores the user ID, parent comment ID, and use those to relate users to comments.

A lot of what you're trying to do sounds like it could be achieved by using an existing blogging platform or CMS, so that might be something you want to look into first.

thx i will check it