@@ -68,7 +68,7 @@ marketing:
6868 Enjoying programming all over again. It's been a while since I wrote Rust, but getting a good hang of it.
6969
7070stages :
71- - slug : " init"
71+ - legacy_slug : " init"
7272 name : " Print page size"
7373 difficulty : very_easy
7474 description_md : |-
@@ -120,7 +120,7 @@ stages:
120120 prints metadata related a SQLite database, and you'll implement one of these values: the database page size. You'll
121121 do this by parsing a file that uses the [SQLite database file format](https://www.sqlite.org/fileformat.html).
122122
123- - slug : " table_count"
123+ - legacy_slug : " table_count"
124124 name : " Print number of tables"
125125 difficulty : hard
126126 description_md : |-
@@ -164,7 +164,7 @@ stages:
164164 implement functionality to print the number of tables. You'll do this by parsing a file that uses the
165165 [SQLite database file format](https://www.sqlite.org/fileformat.html).
166166
167- - slug : " table_names"
167+ - legacy_slug : " table_names"
168168 name : " Print table names"
169169 difficulty : hard
170170 description_md : |-
@@ -196,7 +196,7 @@ stages:
196196 [`.tables`](https://www.sqlite.org/cli.html#special_commands_to_sqlite3_dot_commands_). Instead of just printing
197197 the count of tables like in the previous stage, you'll print out the names of tables too.
198198
199- - slug : " row_counts"
199+ - legacy_slug : " row_counts"
200200 name : " Count rows in a table"
201201 difficulty : medium
202202 description_md : |-
@@ -234,7 +234,7 @@ stages:
234234 In this stage, your sqlite3 implementation will need to execute a SQL statement of this form:
235235 `SELECT COUNT(*) FROM <table>`.
236236
237- - slug : " read_single_column"
237+ - legacy_slug : " read_single_column"
238238 name : " Read data from a single column"
239239 difficulty : hard
240240 description_md : |-
@@ -284,7 +284,7 @@ stages:
284284 In this stage, your sqlite3 implementation will need to execute a SQL statement of this form:
285285 `SELECT <column> FROM <table>`.
286286
287- - slug : " read_multiple_columns"
287+ - legacy_slug : " read_multiple_columns"
288288 name : " Read data from multiple columns"
289289 difficulty : hard
290290 description_md : |-
@@ -315,7 +315,7 @@ stages:
315315 This stage is similar to the previous one, just that you'll read data from multiple columns instead of just one.
316316 In this stage, your sqlite3 implementation will need to execute a SQL statement of this form: `SELECT <column1>,<column2> FROM <table>`.
317317
318- - slug : " where"
318+ - legacy_slug : " where"
319319 name : " Filter data with a WHERE clause"
320320 difficulty : hard
321321 description_md : |-
@@ -343,7 +343,7 @@ stages:
343343 In this stage, you'll filter records based on a `WHERE` clause. You'll assume that the query can't be served by
344344 an index, so you'll visit all records in a table and then filter out the matching ones.
345345
346- - slug : " table_scan"
346+ - legacy_slug : " table_scan"
347347 name : " Retrieve data using a full-table scan"
348348 difficulty : hard
349349 description_md : |-
@@ -385,7 +385,7 @@ stages:
385385 In this stage, you'll filter records based on a `WHERE` clause. You'll assume that the query can't be served by
386386 an index, so you'll visit all records in a table and then filter out the matching ones.
387387
388- - slug : " index_scan"
388+ - legacy_slug : " index_scan"
389389 name : " Retrieve data using an index"
390390 difficulty : hard
391391 description_md : |-
0 commit comments