17 | Create Database Tables in MySQL PHP Tutorial | 2023 | Learn PHP Full Course for Beginners 

Sorry bro for the loss

😢

😢Sorry to hear this all the best

:(

Sorry to hear. Can imagine you needed some time to it.

Learning php at 73??? You're my Hero.

@@SamBoxEthiopia Thank you SanBox Ethiopis, I am NOT a Hero! I started out with electricity “talking to me”. Just into high school (in about 1966 or so) I decided I was to lazy to go across the room to turn my TV on and off. I made a WIRED remote control that would turn the TV on and off along with changing the volume. In 1966 NOBODY had ever heard of remote control on TV’s. After high school I went to an electronics school. In 1971 I was a certified electronics technician in the state of Missouri. I only did that for about three years of so. Then I went to work as a welder, with many welding jobs throughout my life. In about 1978 or 79 I started working at of the Pacific Northwest biggest saw mills. In 1983 I touched my FIRST computer. Make sure you get the date right. That was BEFORE Bill Gates was a household name. I have been addicted to them DAMN things every since. I welded in several jobs until about 2003 or so. Then I became a videographer, not long after that I got several jobs as a professional videographer. I retired in 2013 (or so I thought) I still have three to seven video shoots per year, I also help out friends out welding all the time. Soooo, now WHY NOT learn PHP. I am doing pretty well but I will probably never make any money with PHP. After all who wants to hire a 73 year old man. Besides that, I DO NOT WANT A FULL TIME JOB. So here I am setting in front of my two 27” monitors with a gaming system that is very very powerful. NO, I am not a gamer. But like I said I am addicted to computers. So I am not a hero by any means. Just someone that NEVER figured out what to do with my life. (:

You are correct, you would be better off doing a inner join SQL statement. 🙂

​@@Dani_Krossing Thanks! I had the same question. But to clarify a bit more, we don't need to add the "username" column in the "comments" table, right? We can just reference it to the "users" table through the foreign key "users_id", correct? Is there any reason to actually have this kind of "redundant" information in a database table? (On that matter, do you have any video about the key principles of structuring your SQL database? - With your teaching skills, I might finally be able to grasp that... 😅) Oh, and thank you so much for all this useful information and the perfectly structured course!!

Your data will “overflow” and create errors. But unless you plan on creating a website that uses billions of rows in one table, that won’t happen. IF you plan on having more rows than a INT has storage for, then just use BIGINT instead for the id 🙂 Or if you plan on creating a HUGE commercial site like Facebook, which literally stores billions of messages a day, I can imagine they use custom databases with multiple databases specifically for messages only hehe.

@@Dani_Krossing interesting. Yeah I don't plan on ever having 4 billion users on a website lol

Once I'm done with this MySQL part of the course, the plan is to teach that. 🙂 I do have a older PHP course that shows it too, if you need it now.

Please do python language also

​@@Dani_Krossing I need complete video of web-based application design with your explanation. I think it's useful for student

Including the `username` column in the `comments` table alongside the `users_id` foreign key column depends on your specific requirements and design considerations. Having the `username` column in the `comments` table can be beneficial in scenarios where you frequently need to display comments along with the username without having to join the `users` table every time. This denormalization can improve query performance, especially in cases where you're frequently retrieving comments and displaying them with usernames, as it eliminates the need for a join operation. However, if you're concerned about data redundancy or prefer a more normalized database design, you can omit the `username` column from the `comments` table and rely solely on the `users_id` foreign key to associate comments with users. In this case, when you need to display a comment along with the username, you would perform a join operation between the `comments` and `users` tables to retrieve the username. In summary, whether to include the `username` column in the `comments` table depends on factors such as performance considerations, data redundancy, and your specific application requirements. Both approaches are valid and have trade-offs that you should consider based on your particular use case. At least this is what I got from chatGPT lol.

If you would like to join, there is a link for either my Patreon, or my RU-vid memberships, in the bottom of the description. 🙂

What is the full SQL that you tried to submit?

@@Dani_Krossing I’m not sure what you mean by that but I did everything that’s in the video. It seems it only works if I do CURRENT_TIMESTAMP instead of CURRENT_TIME. Is there a difference?

​@@Dani_Krossing I have the same problem: CREATE TABLE users ( id INT(11) NOT NULL AUTO_INCREMENT, username VARCHAR(30) NOT NULL, pwd VARCHAR(200) NOT NULL, email VARCHAR(100) NOT NULL, created_at DATETIME NOT NULL DEFAULT CURRENT_TIME, PRIMARY KEY(id) );

im getting the same error.... did you find the solution? this is my error #1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'CURRENT_TIME, PRIMARY KEY (id) )' at line 6

i'm getting the same thing. from what i can gather from searching it, DATETIME will be obsolete in about 15 yrs? people seemed to lean toward using timestamp so...i just used that instead and stopped getting the error lol

That’s not a table 🙂 that’s a button you can click to create a new table

@@Dani_Krossing OK. Thank you very much for your time.

Because the ID has to be unique to that particular entry, and not based on other tables. Otherwise a bunch of issues can happen. Primary Keys should not be Foreign Keys.

The ID is for the table row, which is different. There HAS to be a unique id for all rows of data, which isn’t up to the user to decide. Having the ID be a number, also makes it easier to list them all out if needed.