Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

Database Naming Conventions - Pivot Tables? 16 Aug 2016 12:33 #14447

Hi,
I've noticed people here are using the term "Pivot" table for what was called an XRef table in the JCook docs.

Outside of here, I think it is called a Join Table, Relational Table, Associative Table or Link Table. The Wikipedia used to call it a Junction Table - but now calls it Associative table - en.wikipedia.org/wiki/Associative_entity . Personally I'm one for "Join Table".

There is a discussion on this topic here on stackoverflow...
stackoverflow.com/questions/1429908/is-t...-table-in-a-database

Is it correct to use the term Pivot table? People confuse it with Excel Pivot tables. I am relatively old, self taught and isolated from the rest of the world - so maybe I'm just confused an ignorant? Please correct me.

Should we have a Database Definitions page (or add it to the Glossary in docs) so we are all talking the same language?

I don't know about you guys, I'm also used to using the terms "row" and "column". Also FK could be added to the glossary.
Just call me Chris :)

Please Log in or Create an account to join the conversation.

Database Naming Conventions - Pivot Tables? 16 Aug 2016 13:05 #14450

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
You are correct.

I used the pivot Name for the vars for following the FOF naming convention wich is quite good.
But in the docs, I should change that. You are right.

I am redesigning the website, and then I will do the proper documentation.
Coding is now a piece of cake
The following user(s) said Thank You: organicwebs

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.104 seconds

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started