Linux server admin, MySQL/TSQL database admin, Python programmer, Linux gaming enthusiast and a forever GM.

  • 1 Post
  • 162 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle





  • In Uni I ran Gentoo as my daily driver. It was stupid, but I learned a lot.

    Trying and failing to get a working desktop environment, using IRC on the command line to get help from people who knew what they were doing and could advise a dumb kid like me, following their advice and getting a working DE after a reboot was the most hackerman I ever felt. I was convinced I was real hot shit. In actuality, I’d followed the advice to tweak the kernel config to get working drivers :))



  • Please don’t lump trademarks with the rest. Makers have stamped their goods with their mark since ancient times, both as advertising and to signify quality products (and not knockoffs). Swords were especially commonly marked with the smith’s trademark.

    It was illegal to sell bread in ancient Rome without a trademark, for example. The punishments for doing so were harsh, as they wanted to be able to track down the baker if someone sold tainted bread.

    In modern days, they’re useful for customers to know what company they’re buying from.




  • I know someone who got had by a spearfishing call. They knew all the details about his phone contract, sounded 100% legit. The scammer got thousands of dollars in prepaid SIM cards from his account.

    After the police investigation, turned out that the scammer was actually a former employee of the phone company who downloaded a copy of the customer list when he got fired.







  • It’s necessary to split it out into different tables if you have a one-to-many relationship. Let’s say you have a list of driver licenses the person has had over the years, for example. Then you’d need the second table. So something like this:

    SSN_Table

    ID | SSN | Other info

    Driver_License_Table

    ID | SSN_ID | Issue_Date | Expiry_Date | Other_Info

    Then you could do something like pull up a person’s latest driver’s license, or list all the ones they had, or pull up the SSN associated with that license.


  • Theoretically, yeah, that’s one solution. The more reasonable thing to do would be to use the foreign key though. So, for example:

    SSN_Table

    ID | SSN | Other info

    Other_Table

    ID | SSN_ID | Other info

    When you want to connect them to have both sets of info, it’d be the following:

    SELECT * FROM SSN_Table JOIN Other_Table ON SSN_Table.ID = Other_Table.SSN_ID

    EDIT: Oh, just to clear up any confusion, the SSN_ID in this simple example is not the SSN itself. To access that in this example query, it’d by SSN_Table.SSN