MySQL Tutorial 6 – Numeric Data Types




HELP ME! http://www.patreon.com/calebcurry Subscribe to my newsletter: http://eepurl.com/-8qtH Donate!: http://bit.ly/DonateCTVM2.

Original source


22 responses to “MySQL Tutorial 6 – Numeric Data Types”

  1. You remind me of Ferris Bueller. Awesome videos bro. you are breaking it down and using human examples. Thank you soo much. I see you have PHP videos also. Look forward in watching those too.

  2. Bro you are awesome. And never say you don't care about your other videos. People will think that you are not serious in your video. At least that's what I think when u say that. Anyway keep up the good work and thanks. I'm going further with the series. Have a test tomorrow. Wish me good luck! 😀

  3. Caleb, I'm on Tutorial 6 and understand about 80% of the content, and I can't wait to see on screen how all this info. translates. I am impressed by your mathematical skills & knowledge of relevant terms and principals. Thanks for the the lessons! Keep up the great work.

  4. Good point. with a MySQL Primary Key, you can assign it a value yourself, or you can use auto increment which does it for you if you do not put a value. It might be that MySQL assumes the value 0 as no value, making it auto increment to the next highest value.

  5. I'm not sure if starting indexes at 1 is more human friendly than starting indexes at 0, because 99/100 people who are starting to learn MySql have already learned a programming language were indexes start at 0. So, basically, 99/100 people are used to indexes starting at 0 and then MySql is like, 'nope, screw off, our indexes start at 1'.

    There is probably a good reasoning for it starting at 1 though.

    I'm hella tired though, so everything above this sentence might not even make sense … ;D

  6. The value in the primary key field is different than the record number MySQL would assign a row. For example, MySQL may see it as row 0, but we assign in the primary key integer to make it human friendly. If we deleted the first 5 rows, MySQL would then see primary key 6 as row 0. The way MySQL stores rows is not easily apparent to us, and the values of the primary key are not consistent to how MySQL would store the information on a hard disk. The primary key row is only a row for our use.

  7. Yea yea, ok. AI primary keys start at 1 so you lose the 0 as a possibility but the total possibilities of just a BIGINT is 18446744073709551616, you're right.

    Why does it even start at 1? Indexes in every language I know start at 0 and MySql starts indexes at 1, jeez? This also counts for functions using indexes like substr as I recall from your video's.

    Thanks for replying so quickly and for the video's of course, good stuff! Keep it up!

Leave a Reply