Check out v4 of the Fauna CLI
v4 of the Fauna CLI is now in beta. The new version introduces enhancements to the developer experience, including an improved authentication workflow. To get started, check out the CLI v4 quick start. |
collectionDef.replace()
We recommend you use FSL to create and update user-defined functions (UDFs). See FSL function schema. |
Replaces a collection definition.
Description
Replaces all fields in a collection definition, represented as a
Collection
document, with fields from a provided data object. Fields not present in the
data object, excluding the coll
and ts
metadata fields, are removed.
Collection
documents are FQL versions of a database’s FSL
collection schema. Collection
documents
have the CollectionDef type. See
Collections.
Staged schema
If a database has staged schema, this method interacts with the database’s staged schema, not the active schema.
You can’t rename a collection while a database has staged schema.
If the database has no staged schema, using this method is equivalent to making an unstaged schema change. Changes are applied immediately to the database’s active schema.
Unstaged schema changes that trigger an index build may result in downtime where the index is not queryable.
Avoid concurrent schema changes
Concurrent unstaged schema changes can cause contended transactions, even if the changes affect different resources. This includes unstaged changes made using:
-
The Fauna CLI
-
The Fauna Dashboard
-
The Fauna Core HTTP API’s Schema endpoints
A schema change triggers a transaction that validates the entire database schema. To avoid errors, do one of the following instead:
-
Perform unstaged schema changes sequentially
Parameters
Parameter | Type | Required | Description |
---|---|---|---|
data |
Object containing valid
|
Yes |
Document fields for the
For supported document fields, see
The object can’t include the following metadata fields:
|
Return value
Type | Description |
---|---|
Definition for the updated collection, represented as a
|
Examples
Collection.byName("Customer")!.replace({
name: "Customer",
history_days: 0,
migrations: [
{
add_wildcard: {}
}
],
computed_fields: {
cart: {
body: "(customer) => Order.byCustomerAndStatus(customer, \"cart\").first()",
signature: "Order?"
},
orders: {
body: "(customer) => Order.byCustomer(customer)",
signature: "Set<Order>"
}
},
wildcard: "Any",
constraints: [
{
unique: [
{
field: ".email",
mva: false
}
],
status: "active"
}
],
indexes: {
byEmail: {
terms: [
{
field: ".email",
mva: false
}
],
queryable: true,
status: "complete"
}
},
document_ttls: true,
ttl_days: 10,
fields: {
name: {
signature: "String"
},
email: {
signature: "String"
},
address: {
signature: "{ street: String, city: String, state: String, postalCode: String, country: String }"
}
}
})
{
name: "Customer",
coll: Collection,
ts: Time("2099-10-03T21:50:53.550Z"),
migrations: [
{
add_wildcard: {}
}
],
indexes: {
byEmail: {
terms: [
{
field: ".email",
mva: false
}
],
queryable: true,
status: "complete"
}
},
constraints: [
{
unique: [
{
field: ".email",
mva: false
}
],
status: "active"
}
],
wildcard: "Any",
ttl_days: 10,
computed_fields: {
cart: {
body: "(customer) => Order.byCustomerAndStatus(customer, \"cart\").first()",
signature: "Order?"
},
orders: {
body: "(customer) => Order.byCustomer(customer)",
signature: "Set<Order>"
}
},
fields: {
name: {
signature: "String"
},
email: {
signature: "String"
},
address: {
signature: "{ street: String, city: String, state: String, postalCode: String, country: String }"
}
},
history_days: 0,
document_ttls: true
}
Is this article helpful?
Tell Fauna how the article can be improved:
Visit Fauna's forums
or email docs@fauna.com
Thank you for your feedback!