you are viewing a single comment's thread
view the rest of the comments
[–] 33 points 2 years ago (56 children)

You also definitely shouldn't be using String non-monotonic UUIDs for primary keys in a database, like, literally ever, but what the fuck do I know, I just do databases for a living, I'm not the all-knowing GPT code wizard.

  • source
  • hideshow 56 child comments
  • [–] 12 points 2 years ago (6 children)

    If you’re using a new-to-you ORM, and you don’t ever check the docs to see the basic primary key syntax… it’s SQLAchemy, it’s well documented and there’s tons of prior art.

    Also I don’t understand their business case but if a user has a primary key, a unique user ID, and a unique customer ID, then all three of those uniquely identify the customer. (Weird, but there are some plausible explanations.) But then why would you need both the user ID and the customer ID in the subscription table is this some stripe thing I don’t understand or are they just bad at this?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 13 points 2 years ago (3 children)

    20 bucks the datastructure was designed for easiest access from the semantics of whatever du jour js lib they were using for the app

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (48 replies)