65
you are viewing a single comment's thread
view the rest of the comments
[-] gnomicutterance@awful.systems 12 points 3 months ago

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?

[-] froztbyte@awful.systems 13 points 3 months ago

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

[-] froztbyte@awful.systems 12 points 3 months ago

“designed”, rather

Even “derived from” feels too strong a statement. “Was the result of”?

[-] blakestacey@awful.systems 11 points 3 months ago

"Sediment precipitated from"?

[-] sailor_sega_saturn@awful.systems 11 points 3 months ago

20 bucks their database schema was copy pasted from chat-gpt.

[-] gianni@lemmy.ca 10 points 3 months ago

Yes, it's some Stripe thing. Stripe requires you to create a customer to be able to vault payment methods and make charges. However it's possible that not all users in their product require this functionality.

[-] gnomicutterance@awful.systems 8 points 3 months ago

ah, thank you!

this post was submitted on 13 Jun 2024
65 points (100.0% liked)

TechTakes

1276 readers
82 users here now

Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.

This is not debate club. Unless it’s amusing debate.

For actually-good tech, you want our NotAwfulTech community

founded 1 year ago
MODERATORS