Metabase changelog how to#
Metabase changelog code#
Metabase changelog trial#

Switched to flat rate pricing with 14-day trial period.Improved the sources section of our website.Added an option to halt syncs when an associated view has a conflict.Added automated trial expiration notifications.Added a trial duration banner to the console.Added a real-time backfill progress indicator for new syncs.Close is generally availableĬlose is now generally available as a new source! Sync all your leads, contacts, and opportunities right to your production database. wait returns a 200 ok only after we've confirmed that your database is up-to-date and in-sync with Shopify. So, to ensure a recent write – like a new Shopify order – has been synced to your database, you'll call our /wait endpoint. But there's a race condition: it can take a second or two for that change to propagate to your database.

Metabase changelog code#

Sometimes, you want your code to read from your database right after making a change via the API. Those write changes you made will flow down to your Sequin database for you to read again. You read from your database, but write changes back to the upstream API. We advocate for a one-way data flow: data flows from the upstream platform to your Sequin database. (Airtable already supports writes via our special Airtable proxy.) With the /wait endpoint, we're completing the write story for new sources like Stripe, Close, and Shopify. Improved the experience for setting up self-hosted databases.Added platform specific sources pages to the website.Added ORMs, self-hosted databases, and the /wait endpoint to our docs.Added ORMs and the /wait endpoint to the connect modal.Now, you can do this all on your own! Just click on the 'Users' tab and you can invite and manage the users on your team. We've supported teams since we launched, you just needed to ask us to merge your team together into the same organization. Team members can set up new syncs (eg., developer databases), edit existing syncs, or pull up credentials for their database or /wait endpoint.

You can build faster when everyone on your dev team has a Sequin account. Integrate faster by using SQL or your favorite ORM to work with all your conversation data. Twilio is now ready for syncing! We'll sync messages, phone calls, and recordings right to your production database.

Fixed an issue that caused sync statuses to show an error during schema rebuilds.

Added the ability to request an SSH tunnel into your database.This new sync process allows you to add views, triggers, and indexes to your database out of the box. Improved Airtable syncs to handle schema migrations in place, without dropping tables.Improved the onboarding experience to include the proxy, /wait endpoint, and events.Please send us a note if you'd like to start using events. You can work with these events directly in your database or use one of our client libraries to trigger as soon as data you care about changes. When you opt in to events, you'll see a new table in your database called _sync_event that logs every change in the API. Sequin's events let you skip all that work.Įvents are a durable event stream right in the Postgres database we sync for you. This typically requires polling the API, setting up Webhooks, or doing both. You want to know as soon as a payment fails in Stripe, or when a status changes in Airtable. Often, you need to write code that responds to creates, updates, or deletes in an API we sync for you. Add a 'Skip' button during on-boarding.Added docs around our updated usage-based pricing model.Fix situations where the 'Login' and 'Sign up' buttons on landing page would swap.Fix issue of accounts not fully activating after subscribing.But we're looking forward to hear how this approach works for customers so we can iterate from here. It's not a perfect solution this means there will be race conditions around foreign key columns. When B is finally inserted, we put the reference into place. We call it 'lazy foreign keys.' The idea: if we insert row A and row A references row B but row B hasn't been inserted yet, we'll still insert row A but we'll remove the reference to B. We've released our first approach into alpha.

Metabase changelog how to#

We have a few ideas for how to solve this. When inserting a new row, we can't be certain all the rows it references have already been inserted. This is because the ordering of inserts and updates is not guaranteed. Tools and clients like ORMs use foreign keys to determine how tables and columns in a database relate to one another.Īdding foreign keys to a table that is synced from another source presents a unique challenge. And they model the relationships of your database. Foreign keys serve two important functions in databases: They provide 'referential integrity' or the confidence that if one row references another, that other row exists.