Skip to content

Commit

Permalink
Fix typos and scrolling
Browse files Browse the repository at this point in the history
  • Loading branch information
José Valim committed Jul 17, 2019
1 parent e69c4d2 commit 6a47977
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 3 deletions.
2 changes: 1 addition & 1 deletion guides/howtos/Dynamic queries.md
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ By using dynamic fragments, we can decouple the processing of parameters from th

## Building dynamic queries

Let's go back to the original problem. We want to build a search functionality where the user can configure how to traverse all posts in many different ways. For example, the user may choose how to order the data, filter by author and category, as well as select posts published after a certain daate.
Let's go back to the original problem. We want to build a search functionality where the user can configure how to traverse all posts in many different ways. For example, the user may choose how to order the data, filter by author and category, as well as select posts published after a certain date.

To tackle this in Ecto, we can break our problem into a bunch of small functions, that build either data structures or dynamic fragments, and then we interpolate it into the query:

Expand Down
7 changes: 5 additions & 2 deletions guides/howtos/Multi tenancy with query prefixes.md
Original file line number Diff line number Diff line change
Expand Up @@ -266,8 +266,11 @@ end

## Summing up

Ecto provides many conveniences for working with querying prefixes. Those conveniences allow developers to configure prefix with different level of granularity:
Ecto provides many conveniences for working with querying prefixes. Those conveniences allow developers to configure prefixes with different precedence, starting with the highest one:

connection prefixes < schema prefix < query/struct prefixes < from/join prefixes
1. from/join prefixes
2. query/struct prefixes
3. schema prefixes
4. connection prefixes

This way developers can tackle different scenarios, from production requirements to multi-tenant applications.

0 comments on commit 6a47977

Please sign in to comment.