Conversation

Notices

1. Embed this notice
   eal (eal@post.ebin.club)'s status on Wednesday, 07-Aug-2024 19:32:24 JST eal

   in reply to

   • Cobalt
   @cobalt yeah it's bad for user-facing IDs for those reasons (and leaking the amount of rows, etc), but every table is not readable by users (or you can have a situation like my $dayjob codebase where those things don't matter at all)
   sequential keys get you more efficient queries in some databases, I don't know mysql, they're not bad as a hard rule
   • lainy likes this.
   • Embed this notice
     Cobalt (cobalt@musicians.today)'s status on Wednesday, 07-Aug-2024 19:32:25 JST Cobalt

     in reply to

     @eal it's not a good idea to use sequential IDs as then you could just guess someone's ID, doesn't really matter in this context as it's just for practice but it's bad practice

   • Embed this notice
     eal (eal@post.ebin.club)'s status on Wednesday, 07-Aug-2024 19:32:27 JST eal

     in reply to

     • Cobalt
     @cobalt What's wrong with sequential IDs in mysql?
   • Embed this notice
     Cobalt (cobalt@musicians.today)'s status on Wednesday, 07-Aug-2024 19:32:28 JST Cobalt

     teacher is teaching mysql and they're using sequential IDs