94f5e790f6
Currently, an optimized DB update (simple data => no delete-and-create-row) does the following: 1. sql UPDATE 2. sql SELECT This PR reduces this further to one single DB call for simple collections: 1. sql UPDATE with RETURNING() This only works for simple collections that do not have any fields that need to be fetched from other tables. If a collection has fields like relationship or blocks, we'll need that separate SELECT call to join in the other tables. In 4.0, we can remove all "complex" fields from the jobs collection and replace them with a JSON field to make use of this optimization --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1210803039809814
23 lines
592 B
TypeScript
23 lines
592 B
TypeScript
export const postsSlug = 'posts'
|
|
export const errorOnUnnamedFieldsSlug = 'error-on-unnamed-fields'
|
|
|
|
export const defaultValuesSlug = 'default-values'
|
|
|
|
export const relationASlug = 'relation-a'
|
|
|
|
export const relationBSlug = 'relation-b'
|
|
|
|
export const pgMigrationSlug = 'pg-migrations'
|
|
|
|
export const customSchemaSlug = 'custom-schema'
|
|
|
|
export const placesSlug = 'places'
|
|
|
|
export const fieldsPersistanceSlug = 'fields-persistance'
|
|
|
|
export const customIDsSlug = 'custom-ids'
|
|
|
|
export const fakeCustomIDsSlug = 'fake-custom-ids'
|
|
|
|
export const relationshipsMigrationSlug = 'relationships-migration'
|