úÎ!‘Šô4      !"#$%&'()*+,-./0123None456 Fpersistent-paginationDUsers aren't required to put a value in for the range - a value of 40 is equivalent to saying "unbounded from below."persistent-pagination€A datatype describing the min and max value of the relevant field that you are ranging over in a non-empty sequence of records.persistent-paginationWhether to sort by ASC or DESC! when you're paging over results.persistent-paginationThe amount of records in a Page of results. persistent-pagination Modify the  according to the ) that was provided by the query and the .    None "#&'0456>SXIŽ persistent-paginationA  record typp describes a list of records and enough information necessary to acquire the next page of records, if possible.persistent-paginationThe collection of records.persistent-paginationIThe count of records in the collection. If this number is less than the  field, then a call to $ will result in 4.persistent-pagination!The minimum and maximum value of typ in the list.persistent-pagination8The desired range in the next page of values. When the   is  Ascending , then the \ value will increase with each page until the set of data is complete. Likewise, when the   is  Descending , then the 0 will decrease until the final page is reached.persistent-pagination¶The field to sort on. This field should have an index on it, and ideally, the field should be monotonic - that is, you can only insert values at either extreme end of the range. A  created_at– timestamp or autogenerated ID work great for this. Non-monotonic keys can work too, but you may miss records that are inserted during a traversal.persistent-pagination/The extra filters that are placed on the query.persistent-paginationThe desired size of the  for successive results. persistent-paginationWhether to sort on the  in  Ascending or  Descending6 order. The choice you make here determines how the  changes with each page.!persistent-paginationZStream entities out of the database, only pulling a limited amount into memory at a time.You should use this instead of 5 because 5ÿ doesn't really work. It doesn't work at all in MySQL, and it's somewhat sketchy with PostgreSQL and SQLite. This function is guaranteed to use only as much memory as a single page, and if you tune the page size right, you'll get efficient queries from the database.There's an open issue for 5 not working:  1https://github.com/yesodweb/persistent/issues/657 GitHub Issue."persistent-pagination Convert a  typ into a list of 6s for the query. The " is treated as an exclusive range.#persistent-paginationGet the first 2 according to the given criteria. This returns a 7 f, because there may not actually be any records that correspond to the query you issue. You can call R on the result object to get the row of records for this page, and you can call $ with the , object to get the next page, if one exists.FThis function gives you lower level control over pagination than the ! function.$persistent-paginationRetrieve the next  of data, if possible.!persistent-paginationThe filters to apply.persistent-pagination¶The field to sort on. This field should have an index on it, and ideally, the field should be monotonic - that is, you can only insert values at either extreme end of the range. A  created_at˜ timestamp or autoincremented ID work great for this. Non-monotonic keys can work too, but you may miss records that are inserted during a traversal.persistent-paginationHow many records in a pagepersistent-paginationAscending or descendingpersistent-paginationThe desired range. Provide  Nothing Nothing) if you want everything in the database.#persistent-paginationThe filters to apply.persistent-pagination¶The field to sort on. This field should have an index on it, and ideally, the field should be monotonic - that is, you can only insert values at either extreme end of the range. A  created_at– timestamp or autogenerated ID work great for this. Non-monotonic keys can work too, but you may miss records that are inserted during a traversal.persistent-paginationHow many records in a pagepersistent-paginationAscending or descendingpersistent-paginationThe desired range. Provide  Nothing Nothing) if you want everything in the database.  !"#$ !"#$None "#&'0456>SXŒé%persistent-paginationA % record typp describes a list of records and enough information necessary to acquire the next page of records, if possible.!This is a distinct type from the % in Database.Persist.Pagination because the ,“ field needs a different type. As a result, some of this stuff is duplicated. It's possible that this can be fixed and more code could be shared.'persistent-paginationThe collection of records.(persistent-paginationIThe count of records in the collection. If this number is less than the - field, then a call to 2 will result in 4.)persistent-pagination!The minimum and maximum value of typ in the list.*persistent-pagination8The desired range in the next page of values. When the . is  Ascending , then the \ value will increase with each page until the set of data is complete. Likewise, when the . is  Descending , then the 0 will decrease until the final page is reached.+persistent-pagination¶The field to sort on. This field should have an index on it, and ideally, the field should be monotonic - that is, you can only insert values at either extreme end of the range. A  created_at– timestamp or autogenerated ID work great for this. Non-monotonic keys can work too, but you may miss records that are inserted during a traversal.,persistent-pagination/The extra filters that are placed on the query.-persistent-paginationThe desired size of the % for successive results..persistent-paginationWhether to sort on the + in  Ascending or  Descending6 order. The choice you make here determines how the * changes with each page./persistent-paginationZStream entities out of the database, only pulling a limited amount into memory at a time.You should use this instead of 5 because 5ÿ doesn't really work. It doesn't work at all in MySQL, and it's somewhat sketchy with PostgreSQL and SQLite. This function is guaranteed to use only as much memory as a single page, and if you tune the page size right, you'll get efficient queries from the database.There's an open issue for 5 not working:  1https://github.com/yesodweb/persistent/issues/657 GitHub Issue.0persistent-pagination Convert a  typ into a 8" that operates on the range. The " is treated as an exclusive range.1persistent-paginationGet the first %2 according to the given criteria. This returns a 7 %f, because there may not actually be any records that correspond to the query you issue. You can call 'R on the result object to get the row of records for this page, and you can call 2 with the %, object to get the next page, if one exists.FThis function gives you lower level control over pagination than the / function.2persistent-paginationRetrieve the next % of data, if possible.3persistent-paginationVAn empty query value to pass to the functions when you don't have any filters to run./persistent-paginationThe filters to apply.persistent-pagination¶The field to sort on. This field should have an index on it, and ideally, the field should be monotonic - that is, you can only insert values at either extreme end of the range. A  created_at˜ timestamp or autoincremented ID work great for this. Non-monotonic keys can work too, but you may miss records that are inserted during a traversal.persistent-paginationHow many records in a pagepersistent-paginationAscending or descendingpersistent-paginationThe desired range. Provide  Nothing Nothing) if you want everything in the database.1persistent-paginationThe filters to apply.persistent-pagination¶The field to sort on. This field should have an index on it, and ideally, the field should be monotonic - that is, you can only insert values at either extreme end of the range. A  created_at– timestamp or autogenerated ID work great for this. Non-monotonic keys can work too, but you may miss records that are inserted during a traversal.persistent-paginationHow many records in a pagepersistent-paginationAscending or descendingpersistent-paginationThe desired range. Provide  Nothing Nothing) if you want everything in the database. %&-')*+,(./0123%&-')*+,(./0123SafeÏ9:;<=>?@A       !"#$%& !"#$%&'()*+,-+./()0123456789:;<4persistent-pagination-0.1.1.0-HdsNE2MtHtlKzAyCXnGW91!Database.Persist.Pagination.TypesDatabase.Persist.PaginationDatabase.Esqueleto.PaginationPaths_persistent_pagination DesiredRangeRangerangeMinrangeMax SortOrderAscendDescendPageSize unPageSize bumpPageRange $fMonoidRange$fSemigroupRange $fEqPageSize$fShowPageSize $fEqSortOrder$fShowSortOrder $fEqRange $fShowRange$fFunctorRange$fFoldableRange$fTraversableRangePage pageRecordspageRecordCount pageRangepageDesiredRange pageField pageFilterspageSize pageSortOrderstreamEntitiesrangeToFiltersgetPagenextPage emptyQuerybase GHC.MaybeNothing(persistent-2.10.0-AKwOUVihi7vE8aCCkhfrYi#Database.Persist.Class.PersistQuery selectSource$Database.Persist.Class.PersistEntityFilterMaybe&esqueleto-3.0.0-8u3uyDqkyXC4HIMaKfRY99$Database.Esqueleto.Internal.InternalSqlQueryversion getBinDir getLibDir getDynLibDir getDataDir getLibexecDir getSysconfDirgetDataFileName