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

  • 7 Posts
  • 452 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle








  • It’s really hard to find on Google considering this was an academic paper from 3 years ago, but generally the big problem with polling in Russia is that for obvious reasons Russians are scared to give their honest opinions. If asked over the phone what they think of Putin, every politically neutral Russian and even some anti-Putin activists will say they approve.

    From memory, the methodology they used was to give 3 propositions unrelated to Putin (less contentious policy decisions) and the respondents were only asked how many of the statements they agreed with, not which ones. Then they did the same thing again with 4 propositions (4th one being if they approve of Putin), then a 3rd time (this time with the 4th one being if they disapprove). With those 3 datasets, you can then essentially subtract the 3 unrelated propositions from the 4th one they actually cared about, all without requiring the respondent to actually state their opinion on the phone.








  • Support networks are so incredibly important to parents. Don’t have kids of my own, but am helping with my sibling’s kids. Babysitting and just general support split with my parents. Thankfully, they don’t need financial help but that’d be on the cards if it came to it.

    Support networks like this, whether it’s family, neighbours, friends or some combination is almost mandatory if you’re not very wealthy. It takes a village to raise a child, after all.




  • 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