Included: removal of remains of GraphQL adaptation. IMO the after/before behaviour is actually pretty badly defined if entities can be deleted, and delivers complexity trying to fix behaviour that users generally expect and are comfortable coping with. Of course special cases _do_ justify going extra length to provide consistent pagination.
		
			
				
	
	
		
			15 lines
		
	
	
		
			166 B
		
	
	
	
		
			SQL
		
	
	
	
	
	
			
		
		
	
	
			15 lines
		
	
	
		
			166 B
		
	
	
	
		
			SQL
		
	
	
	
	
	
| 
 | |
| SELECT 
 | |
|     id,
 | |
|     owner,
 | |
|     name,
 | |
|     notes,
 | |
|     schedule,
 | |
|     created_at
 | |
| FROM
 | |
|     tasks
 | |
| WHERE
 | |
|     owner = $1
 | |
| ORDER BY created_at ASC, id ASC
 | |
| LIMIT $2 OFFSET $3;
 |