And Open Source Software Fund Video live streaming and more Video written content We're hiring What's next for the release and New Features Our engineers have been hard at work releasing a new version with many improvements and new features.upcoming features on our roadmap Latest news. We once released a regression of course and fixed it very quickly. A new major version plus breaking changes. Bumped a lot of features into general release. Released some new preview features and improvements over the past three months. In case you missed it, we hosted a livestream covering issues you might encounter when upgrading to and how to resolve them Feature Upgrade to General Availability Improved support for indexing we introduced in and promoted it to general availability. Now you can configure the index in the schema using properties to define the type of index that should be created in the database. You can configure the following .
Index sort order and explicit unique constraints on the length of the relationship in the schema. From the beginning the relationship must be marked with an attribute on the side of the relationship that co photo editing servies ntains the foreign key. Previously relationship fields were implicitly treated as unique behind the scenes. This field is also added explicitly at runtime. Breaking changes Please see our upgrade paths for detailed instructions and steps to follow. Removed support for using implicit relationships Removed use of parameters Previously parameters were optional when using relationships. This is because the only valid values are so removing this parameter makes it clear what can and cannot be changed. See our documentation to learn more about implicit relationships. Breaking changes Please see the upgrade guide for detailed instructions and steps to follow. Enforcing uniqueness of referenced fields in arguments in AND relationships now enforces that fields on one side are unique when used.
To resolve this issue add the or attribute to the foreign key field in the schema. Breaking Changes To learn how to upgrade to a version please see our upgrade guide. Remove undocumented support for aliases We are deprecating the string alias keyword. This keyword will now be used exclusively in defined embedded documents. You are encouraged to remove any type aliases that use this keyword from your schema. Remove prefixes from protocols we no longer support. We encourage you to use this prefix when using. Better String Literal Syntax String literals in start patterns need to follow the same rules as strings in . This mainly changes the escaping of some special characters. You can find more details about the specifications here To resolve this issue resolve the validation errors in the schema.
發表於 2023-12-31 14:54:39
