Best Approach for Atomic Data Replacement in a Table Using SeaORM

[Jason5Lee]

I have a requirement to atomically replace all data in a table with new data converted from a specific source, potentially involving massive volumes (millions of rows). Using a single transaction to insert all data directly seems risky. My current approach involves creating a temporary table with an identical schema, inserting the new data into this temporary table, and then atomically replacing the original table. This method appears theoretically viable (e.g., MySQL's RENAME TABLE can swap tables, assuming temporary tables are safely discardable).

The challenge lies in implementing this with SeaORM due to two main hurdles:

1. SeaORM doesn't easily allow custom table names for data inserts.
2. Operations like RENAME and DROP lack native ORM support.

What are the best practices to address these issues? Are there alternative methods better suited for atomic data replacement in SeaORM?

[tyt2y3]

I think your approach is sound. for 1, you can use two identical entities with different table names
for 2, I think you can use a raw SQL statement

[Jason5Lee]

For 1, is there a convenient way to create an identical Entity with only a different table, based on an existing Entity? For 2, how can I obtain the quoted table name from an Entity to use in SQL concatenation?