Hi im getting this behavior using server side pagination
my sql query is like this
SELECT
DISTINCT on (c.apellidos)
o.fechaproxima_llamada,
c.ubicacion,
c.notas,
c.nombres,
c.apellidos,
c.cedula,
c.sector,
c.empresa,
c.acreedor,
c.analista,
c.sucursal,
o.motivo,
c.ps,
c.fecha_nacimiento,
c.sexo,
c.usuario,
DATE_PART('YEAR', AGE(CURRENT_DATE, c.fecha_nacimiento)) as edad
FROM
tbl_clientes c
INNER JOIN tbl_observaciones o ON c.idclave_nombre = o.idclave_nombre
WHERE (
{{ !cedula.value }}
OR c.cedula LIKE {{ cedula.value }}
)
AND
({{ !analista.value }}
OR c.analista ILIKE {{ '%' + analista.value + '%' }})
AND (
{{ !ubicacion.value }}
OR c.ubicacion ILIKE {{ '%' + ubicacion.value + '%' }}
)
AND (
{{ !motivo.value }}
OR o.motivo ILIKE {{ '%' + motivo.value + '%' }}
)
AND (
{{ !sector.value }}
OR c.sector ILIKE {{ '%' + sector.value + '%' }}
)
ORDER BY
c.apellidos,
o.fechaproxima_llamada ASC
LIMIT
{{table1.pagination.pageSize}}
OFFSET
{{table1.pagination.offset}}
how can avoid that? if you see i got some filters, it lookup a dataset, that works but table should be limited to the results items but still showing like all results are in there and allows user to keep changing page, any way to remove that behaviour? heres is my table pagination config
I think so... The wheres and the join. You have a where on o too. Because your count currently is the whole dataset. I could be wrong, give it a whirl.