fnUpdate problem with Server-side processing
fnUpdate problem with Server-side processing
Markus
Posts: 2Questions: 0Answers: 0
I am using the examples/server_side/pipeline.html together with jeditable and paging.
When i change an entry using fnUpdate() the display is correctly updated. The problem starts when i go to the next page and then back. The display is now updated with the old cached data.
Currently i flush the cache manually in the callback functions, but it would be nicer if fnUpdate() would update the pipeline cache.
thanks,
Markus
typo on http://www.datatables.net/api "to can" -> "you can"
When i change an entry using fnUpdate() the display is correctly updated. The problem starts when i go to the next page and then back. The display is now updated with the old cached data.
Currently i flush the cache manually in the callback functions, but it would be nicer if fnUpdate() would update the pipeline cache.
thanks,
Markus
typo on http://www.datatables.net/api "to can" -> "you can"
This discussion has been closed.
Replies
The fnUpdate function isn't really suitable for server-side processing, regardless of the pipelining. Really what needs to happen is that the server be informed of the new data, so it can be updated. Otherwise, next time the page is drawn, it will show the information from the database. You might have worked around this my sending an Ajax update to the server, but fnUpdate will still cause a redraw. So what needs to happen is that the pipeline cache be cleared out to it will request the data again.
Allan
The whole-cache-flush is working. I'll leave it until someone complains ;)
Markus