FaunaDB Client Drivers and FQL v10: Migration Rollback Strategy

Integration Boundary: Application Driver and FQL Versioning

FaunaDB introduced a significant shift from FQL v4 to FQL v10, introducing a new query language and driver requirements. Because these versions are not interoperable, application code written for v10 cannot execute against v4 endpoints, and vice versa.

When performing a migration to FQL v10, the recovery process typically involves rolling back the application code and the client driver version. However, if the migration included destructive schema changes or data transformations performed via application logic, the database state remains altered despite the driver rollback.

Since Fauna is a managed service, there is no native "undo" for service-side API transitions or application-driven data migrations. This creates uncertainty regarding the safest recovery path when a v10 deployment fails after data has been mutated.

• Does Fauna provide a supported mechanism to revert schema changes automatically when rolling back driver versions?
• In the absence of point-in-time recovery, what is the recommended verification process to ensure a document export is compatible with a downgraded driver version?