@@ -51,7 +51,7 @@ meaning of the query.
51
51
52
52
In some workloads, it's easy. Transactional/operational workloads like
53
53
multi-tenant SaaS apps or the Internet of Things distribute tables by tenant or
54
- device. Queries are usually scoped to a tenant- or device-ID.
54
+ device. Queries are scoped to a tenant- or device-ID.
55
55
56
56
For instance, in our [ multi-tenant
57
57
tutorial] ( tutorial-design-database-multi-tenant.md#use-psql-utility-to-create-a-schema )
@@ -129,12 +129,12 @@ SELECT *
129
129
130
130
In general, when joining distributed tables, try to include the distribution
131
131
column in the join conditions. However, when joining between a distributed and
132
- reference table you don't need to do this , because reference table contents are
132
+ reference table it's not required , because reference table contents are
133
133
replicated across all worker nodes.
134
134
135
- If it seems inconvenient to add the additional filters to all your queries,
136
- keep in mind there are helper libraries for several popular application
137
- frameworks that make it easier. Here are instructions:
135
+ If it seems inconvenient to add the extra filters to all your queries, keep in
136
+ mind there are helper libraries for several popular application frameworks that
137
+ make it easier. Here are instructions:
138
138
139
139
* [ Ruby on Rails] ( https://docs.citusdata.com/en/stable/develop/migration_mt_ror.html ) ,
140
140
* [ Django] ( https://docs.citusdata.com/en/stable/develop/migration_mt_django.html ) ,
0 commit comments