• 0 Posts
  • 14 Comments
Joined 21 days ago
cake
Cake day: June 12th, 2025

help-circle

  • I thought Democrats embraced socialism.

    Democrats, the party and politicians, no. Not even close. As much as Fox News would love you to believe that.

    Democrats, the voters, much more so. The majority of people in the US are like you. When presented with actual socialist policies, they’re on board. But most people are also not engaged enough in politics to recognize that the Democratic party doesn’t actually believe in socialist policies, they just vote for “the left”. Or, they do recognize it, but feel that they have no better options.












  • That’s a perfectly valid approach, yes. We do exactly this, at work. It’s pretty common, if not ubiquitous, to have your database schema consist of not only structure, but data as well. We call it static data, and it’s all defined in deployable scripts, just like our tables and views are. If ISO makes changes to the dataset, then it’s just a table update to match it. And ISO is nice about keeping backwards compatibility inb their standards.

    Since this is not strictly your own data, you could also go with just storing the code value on your tables, and letting the UI layer do the lookup, either with built-in features of your language/framework, or with a static csv file, like you mention. You may not want to do this for static data that is entirely your own, like, say, a status or type enum, since it makes your database schema less-self-descriptive, and more prone to becoming invalid.

    You could also set the country code up as a not-strictly-enforced foreign key, where your app will lookup additional info (E.G. the proper name) for a country code, if it’s a standard one, but just skip that if it’s not a standard one.

    It’s up to you what you think is most appropriate.