For years, the productivity space has been dominated by a cold war between spreadsheet warriors (Excel, Google Sheets) and note-taking enthusiasts (Notion, Obsidian). But a hybrid app has been quietly heating up, and recently, it hit a boiling point.
Memento Database is currently trending, and it’s not just because of a slick interface update. It is trending because it solves the one problem other apps ignore: Context.
If you have ever tried to track a wine collection in Google Sheets, you know the pain of data entry. If you’ve tried to manage a rental property in Notion, you know the frustration of lacking calculation power. Memento bridges that gap, and the "hot" new way to use it is transforming it into a fully automated Personal Information System (PIS).
Here is your deep dive into why Memento is having a moment, and how to leverage its most powerful features. memento database tutorial hot
The old way of organizing was folders. The "hot" way is Relational Database Management. Memento excels here.
Unlike simple list apps, Memento allows you to link libraries (tables) together. This is where the magic happens for advanced users.
The "Second Brain" Setup:
By creating a Relation field, you can link the task "Buy paint" to the "Home Renovation" project. When you view the Project entry, Memento automatically rolls up all related tasks and resources into a single dashboard.
The Trend: People are moving their entire CRM (Customer Relationship Management) and ERP (Enterprise Resource Planning) systems out of expensive SaaS subscriptions and into Memento because of how seamless this linking is on mobile.
Spreadsheets are ugly. Memento’s recent updates have leaned heavily into customization, allowing users to build "Dashboards" rather than just lists. The Second Brain in Your Pocket: Why Memento
The trending tutorial right now is building an Inventory Dashboard.
This visual pivot makes Memento feel like a premium, bespoke app designed specifically for you, rather than a generic database tool.
When a user saves a document, we do two things inside a database transaction: Library A: Projects (Home Renovation, Learning Spanish)
documents table.document_history.// hot-memento.js
const saveDocumentState = async (docId, newTitle, newContent, userId) =>
const client = await pool.connect();
try catch (err)
await client.query('ROLLBACK');
throw err;
finally
client.release();
;
Decade → Type Formula (JavaScript)const year = record.getFieldValue("Release Year");
if (!year) return "";
return Math.floor(year / 10) * 10 + "s";