Airtable is a powerful cloud-based software that combines spreadsheets and databases, offering real-time collaboration and customizable features for efficient task management1.
Based on our record, Airtable seems to be a lot more popular than Liquibase. While we know about 129 links to Airtable, we've tracked only 5 mentions of Liquibase. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
For the backend, I opted for Airtable as a database. It's a simple, no-code solution that I've used before. It's not the most powerful database, but it's perfect for a project like this. I could easily add, edit, and delete records, and it has an embeddable form functionality that I used for user submissions. - Source: dev.to / 3 months ago
Airtable.com โ Looks like a spreadsheet, but it's a relational database unlimited bases, 1,200 rows/base, and 1,000 API requests/month. - Source: dev.to / 5 months ago
The ?XXXXX part of the URL identifies the type of interface page it is. Just copy that and then your formula is just "https://airtable.com.../...?XXXXXX=" & RECORD_ID() I'm not sure it works in every type of interface page (where you've started from a blank page for example). There has to be something to identify the record viewed from the page, if you see what I mean. Source: 10 months ago
So I started building something on airtable.com that would allow me to easily track updates for each batch. What in your experience would make sense to track that I may be missing? Source: 11 months ago
For character sheets, timelines and having records of chapters and scenes, I really really love Airtable. I have some examples here. Source: 12 months ago
As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: over 2 years ago
I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: over 2 years ago
Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: over 2 years ago
I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: over 2 years ago
Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago
Asana - Asana project management is an effort to re-imagine how we work together, through modern productivity software. Fast and versatile, Asana helps individuals and groups get more done.
Flyway - Flyway is a database migration tool.
Trello - Infinitely flexible. Incredibly easy to use. Great mobile apps. It's free. Trello keeps track of everything, from the big picture to the minute details.
Slick - A jquery plugin for creating slideshows and carousels into your webpage.
Microsoft Teams - Microsoft Teams provides the enterprise-level security, compliance and management features you expect from Office 365, including broad support for compliance standards, and eDiscovery and legal hold for channels, chats, and files.
Sqitch - Sqitch is a standalone database change management application without opinions about your database engine, development environment, or application framework.