From 03f11745b5dc22fe837e096f75a5ff48be23f4d8 Mon Sep 17 00:00:00 2001 From: Kewin Szlezingier <77052270+kewinzaq1@users.noreply.github.com> Date: Sun, 1 Oct 2023 19:41:30 +0200 Subject: [PATCH] fix: typo (#10) --- .../09.optimize/02.problem.multi-column-index/README.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/exercises/09.optimize/02.problem.multi-column-index/README.mdx b/exercises/09.optimize/02.problem.multi-column-index/README.mdx index c642b050..ae29ff10 100644 --- a/exercises/09.optimize/02.problem.multi-column-index/README.mdx +++ b/exercises/09.optimize/02.problem.multi-column-index/README.mdx @@ -1,4 +1,4 @@ -# Multi-Column Index +x# Multi-Column Index 👨‍💼 As we've accumulated more and more users who have more and more notes, we've found that our query for the user list is getting slower and slower and using @@ -323,7 +323,7 @@ go. So in our case, we look at the `WHERE` and then the `ORDER BY` to determine our -indexes. We're referencing the `updatedAt` in the `ORDER BY` and the `owerId` in +indexes. We're referencing the `updatedAt` in the `ORDER BY` and the `ownerId` in the `WHERE`. We need to combine these columns in a single index to optimize this query.