Page cover image

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

Last updated