Supabase

Setup Tips

All synced Supabase tables must have a primary key We use the primary key to keep your data in sync.

Primary keys must be auto-generated (i.e. have a default value) To ensure data consistency, we require primary keys have default values. See Adding default values to primary keys.

Supported Fields

Field	Status
🏷️ Array	✅ Supported
#️⃣ Bigint	✅ Supported
📝 Bit	✅ Supported
☑️ Boolean	✅ Supported
📝 Composite	➡️ Supported (1-Way)
📅 Date	✅ Supported
📅 Daterange	➡️ Supported (1-Way)
🔗 Domain	➡️ Supported (1-Way)
🔘 Enum	✅ Supported
🖇️ Foreign Key	✅ Supported
#️⃣ Geometric	➡️ Supported (1-Way)
#️⃣ Integer	✅ Supported
#️⃣ Interval	➡️ Supported (1-Way)
🗃️Json	✅ Supported
💱 Money	✅ Supported
📝 Network	✅ Supported
#️⃣ Numeric	✅ Supported
⏱️ Range	➡️ Supported (1-Way)
📝 Text	✅ Supported
📝 Textsearch	➡️ Supported (1-Way)
⏱️ Time	➡️ Supported (1-Way)
⏱️ Timestamp	✅ Supported
🆔 Uuid	✅ Supported
🗃️ XML	✅ Supported
🔦 Binary	✖️ Not Yet

Things to Keep in Mind

During Setup

Renaming schema, tables, or columns will break Whalesync mappings If you rename a table/column, you'll need to remap the impacted table/column in Whalesync.

Handy Tips

We support foreign keys (including two-way sync)! In order to sync a foreign key field, you'll need to also sync the table the field references.

Adding ".html" or "_html" to the end of a column name will preserve HTML For example, "text_html", will preserve that column's values as HTML while syncing.

Note that Whalesync does not yet support:

• Whitelisted IP addresses

• Custom SSL/TLS certificates