# Helpful Tip for Noloco MySQL Join Tables: The Important Third Column

**URL:** <https://community.noloco.io/t/helpful-tip-for-noloco-mysql-join-tables-the-important-third-column/1922>\
**Category:** Tips & Tricks ✨\
**Created:** [May 15, 2025, 11:06am UTC](https://community.noloco.io/t/helpful-tip-for-noloco-mysql-join-tables-the-important-third-column/1922 "2025-05-15T11:06:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cor](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/cor/32/1261_2.png) [@cor](https://community.noloco.io/u/cor)\
**Post date:** [May 15, 2025, 11:06am UTC](https://community.noloco.io/t/helpful-tip-for-noloco-mysql-join-tables-the-important-third-column/1922/1 "2025-05-15T11:06:59Z")

</div>

# Quick Tip: Noloco MySQL Join Tables Need Three Columns

I recently discovered something helpful when setting up join tables in my Noloco MySQL implementation that wasn’t immediately obvious to me.

## The Issue & Solution

My join table with just two foreign key columns wasn’t being recognized properly by Noloco. After contacting support, I learned that **join tables should have three columns** : an ID column plus the two foreign keys.

Once I added the primary key ID column, everything worked perfectly!

## Important Note About Reserved Names

Remember that Noloco has reserved field names including `id`, `createdAt`, `updatedAt`, and `uuid`. When you add an `id` column to your join table, Noloco will rename it to “[Table Name] Id” in the interface, but this renaming doesn’t affect functionality.