<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Slick on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/slick/</link>
    <description>Recent content in Slick on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 16:51:00 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/slick/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pagination in Scala with Slick</title>
      <link>https://www.bradcypert.com/pagination-in-scala-with-slick/</link>
      <pubDate>Mon, 02 Sep 2019 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/pagination-in-scala-with-slick/</guid>
      <description>&lt;p&gt;Pagination is the idea that a list of content can be broken into separate pages. When I first heard of pagination, the common practice was to use query params to influence which rows of content was loaded by the server. If you clicked the “next” button on the page, it would reload the page with new query params.&lt;/p&gt;&#xA;&lt;p&gt;Fundamentally, pagination hasn’t changed much, but the landscape in which it exists has changed drastically. While some monolithic apps are still built today, the pattern for modern web development involves APIs and SPAs. In the example we’ll cover today, we’ll talk about the API side of things and use Scala as our example language.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
