# Back to the Future: The Evolving Universal Relation Model

DevFeed: [Back to the Future: The Evolving Universal Relation Model](<https://devfeed.tech/articles/back-to-the-future-the-evolving-universal-relation-model-103409.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.36833>)

Author: Nan Tang, Haixun Wang

Published: 2026-10-28T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Databases](<https://devfeed.tech/sources/arxiv-databases.md>)

Topics: [schema design](<https://devfeed.tech/topics/schema-design.md>), [data-modeling](<https://devfeed.tech/topics/data-modeling.md>), [text2sql](<https://devfeed.tech/topics/text2sql.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [aggregation](<https://devfeed.tech/tags/aggregation.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [application](<https://devfeed.tech/tags/application.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [collections](<https://devfeed.tech/tags/collections.md>), [concepts](<https://devfeed.tech/tags/concepts.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [cs-db](<https://devfeed.tech/tags/cs-db.md>), [database](<https://devfeed.tech/tags/database.md>), [database-schema](<https://devfeed.tech/tags/database-schema.md>), [databases](<https://devfeed.tech/tags/databases.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [evolution](<https://devfeed.tech/tags/evolution.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [future](<https://devfeed.tech/tags/future.md>), [model](<https://devfeed.tech/tags/model.md>)

## AI overview

The Evolving Universal Relation Model (EUR) treats queries as both requests for answers and steps in building a database over documents. Users query the corpus in natural language as though it exposed one conceptual relation; the DBMS evolves the logical schema when new concepts arise, extracts and integrates the facts needed for the query, and decides what database state to retain for later use. This aims to combine flexible, query-first access with reusable database capabilities. The abstract contrasts it with RAG, which retrieves and summarizes evidence but does not itself create reusable, joinable, governed database state, and with schema-first construction, which supports database operations once built but can be costly and brittle when all fields must be modeled upfront. The source presents EUR as a proposal; it does not provide evaluation results.

## Source excerpt

arXiv:2610.36833v1 Announce Type: new Abstract: Document backed analytics need databases that can be built as queries arrive. Enterprises increasingly ask analytical queries over messy document collections such as contracts, invoices, reports, emails, policies, and tickets, where the relevant structure and facts are often not known in advance. RAG can retrieve and summarize supporting evidence, but it does not by itself produce reusable, joinable, governed database state. Schema first construction offers the opposite strength: once a database is built, it supports joins, aggregation, constraints, indexes, optimization, and transactions. Yet for document analytics, fixing the schema and extracting all possible fields upfront is both expensive and brittle, because later queries and new documents often surface concepts that were not modeled before. We propose the Evolving Universal Relation Model (EUR), a query first model for document backed analytics. Users ask natural language queries as if the document corpus exposed one conceptual relation over application concepts. Internally, the DBMS turns each query into controlled database evolution: it updates the logical schema when new concepts are needed, extracts and integrates the facts required to answer the query, and decides what durable database state should remain for future queries. Thus, in EUR, a query is not only evaluated; it also helps construct the database. Document backed analytics becomes query first universal access plus workload-driven database schema and instance evolution.