why mention primary/foreign pivotal attributes buttress names

a integrate new questions plead strategies controlling columns, i rather bewildered learn visualisation embedding thought unfamiliar primary keys buttress names. is

select t1.col_a, t1.col_b, t2.col_z
from t1 middle join t2 t1.id_foo_pk = t2.id_foo_fk

i have confess i have never worked any database component uses arrange scheme, i'm wondering advantages are. proceed i it, once you've learnt n principal tables system, you'll several orders bulk some-more requests those tables.

to spin inclusive development, you'll need learn tables vicious tables, rudimentary tributaries. you'll wish dedicate an good array buttress names memory. simple tasks join twin tables together. devaluate training effort, easiest thing pledge buttress name same both tables:

select t1.col_a, t1.col_b, t2.col_z
from t1 middle join t2 t1.id_foo = t2.id_foo

i speculate that, developer, don't need reminded many columns primary keys, unfamiliar nothing. it's easy adequate feeling during schema you're curious. looking during random

tx middle join ty tx.id_bar = ty.id_bar

... vicious know unfamiliar key? unfamiliar keys vicious wholly database engine itself, grant pledge referential trust right thing during updates deletes.

what problem being solved here? (i know an invitation discuss, feel giveaway so. nonetheless during same time, i am looking an answer, i competence honestly blank something).