In most situations, we will want to avoid displaying an arbitrary number of results to a user in a single response. Instead, we will display a fixed number of results, and give the user an interface to load additional pages of the same size. In an SQL database, pages are typically specified using the OFFSET keyword, but CQL does not have this capability. Instead, we'll use the natural ordering of primary keys to put a lower bound on the key values displayed on a given page.
Let's insert a couple more rows into our table to get a sense of how pagination works using the following INSERT statements:
INSERT INTO "users" ("username", "email", "encrypted_password") VALUES ( 'carol', 'carol@gmail.com', 0xed3d8299b191b59b7008759a104c10af3db6e63a ...
