I can't convince my team that a good database model promotes a good API design and a good UI/UX experience.

Instead, I have to work with a ridiculous table setup.

Imagine, if you will, a table (table B) that references another table (table A) via a foreign key. The FK is a string in both tables. And table A only has one column, which is labeled as "name".

The schema i have to look at it kind of like this:

Table parent
Name varchar(10) primary key

Table child
Name varchar (10),
parent_name varchar(10),
Foreign key (parent_name) references parent (name)

Sorry if the syntax is wrong, a little frustrated having to look at it...

Am I crazy to want to change this table design? Am I missing something? I feel like I'm taking crazy pills, because this is just scratching the surface of the problems I have to deal with.

Ugh. Sending data to a 3rd Party API and for a small subsection of these requests getting error response "A system error occurred". PM: "Who's fault is it? Ours or them?" ... Agh come on, fault is something you can make up, they can make up and entirely irrelevant and unhelpful to anybody. Client: "Why is broken, ideally it would never fail" ... everyone is in goo goo gaa gaa land