• Friday , 24 November 2017

MySQL Tutorial 6 – Numeric Data Types

Code Canyon



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

Original source

3d Ocean

Related Posts

22 Comments

  1. Flor Murillo
    August 12, 2017 at 12:09

    I have seen many videos, I like yours. Quick and resumed.

  2. juan arango
    August 12, 2017 at 12:09

    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.

  3. poiuyanthony
    August 12, 2017 at 12:09

    Made it this far. So far very clear about different data types, Cant wait to see it all come together

  4. Maru Maru
    August 12, 2017 at 12:09

    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! 😀

  5. Miguel R Gaytan
    August 12, 2017 at 12:09

    Thank you for doing these videos, they are really helpful.

  6. osama said
    August 12, 2017 at 12:09

    I going to eat some food too and continue watching great job man thanks

  7. Pontus Freeman
    August 12, 2017 at 12:09

    I like your teaching style, funny and with good examples

  8. Servando Luna Jr
    August 12, 2017 at 12:09

    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.

  9. Taneli Härkönen
    August 12, 2017 at 12:09

    You're awesome man 😀 The cats made my day! xD

  10. Cholowao King Broomz
    August 12, 2017 at 12:09

    Back and said oh like my video, and yes I liked it

  11. Soldie rKing
    August 12, 2017 at 12:09

    thx

  12. mintesinot taye
    August 12, 2017 at 12:09

    smart person. thank
     you!!!

  13. David Barr
    August 12, 2017 at 12:09

    Good. Next one

  14. Kiss Adam
    August 12, 2017 at 12:09

    These are great videos, well done!

  15. Mohammed Salim
    August 12, 2017 at 12:09

    cats :'D

  16. CalebTheVideoMaker2
    August 12, 2017 at 12:09

    Watch series with autoplay: MySQL Tutorial 1 – What is MySQL @CalebCurry

    Donations are greatly needed and appreciated! Click to donate: http://bit.ly/DonateCTVM2

  17. Jesse Steele
    August 12, 2017 at 12:09

    "cuz you can't have two and a half cats… I guess…" lol

  18. MsGencive
    August 12, 2017 at 12:09

    This is awesome… I am a COMPLETE beginner and I have learnt so much thanks to you!

  19. CalebTheVideoMaker2
    August 12, 2017 at 12:09

    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.

  20. de Jager
    August 12, 2017 at 12:09

    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

  21. CalebTheVideoMaker2
    August 12, 2017 at 12:09

    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.

  22. de Jager
    August 12, 2017 at 12:09

    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 Comment

You must be logged in to post a comment.