cache_statement_list does not exist about adl_lrs HOT 4 CLOSED

cache_statement_list is a database table that stores information about statement queries in the case that there are more results than can be returned in one response. see https://github.com/adlnet/xAPI-Spec/blob/master/xAPI.md#42-retrieval-of-statements about the 'more' url.

To fix this error you need to create the table 'cache_statement_list' using this command: python manage.py createcachetable cache_statement_list

Let me know how that goes for you

from adl_lrs.

thank you very much for your answer. I have two PC with the software installed in one of these worked well so take the SQL and create the table manually and it work.

Take to ask advice. We are using ADL_LRS for a research project TEDI (http://www.tedi.cl). Educational books are digital and we are currently doing the piloting. We are in 2 schools with 2 courses of 40 students about which sent an average of 20-30 per class statement (depending on the activity could register up to 80 per student). For now, the LRS has responded well, I know that the project is in development, but decided to use it because in a previous conversation you told me, which was stable for sending and receiving.

I had some problems, for example, to request the URL more he response took too long so I decided to up the number of stament returned directly on setting.py.

Also to consult with parameter limit = 1 it took much more than obtain them all.

Any advice you can give me is valuable for me.

(excuse my bad english)

from adl_lrs.

This is good feedback. We have been testing the LRS to try to get better response times, but our work has been on the 1.0 LRS.

I can say that the filters do take more time, such as limit. This is because of the way we did the filtering. Another issue with limit, is that if there are more results than the limit, we have to store the rest in that cache table and return a more url. This requires more processing as well.

I don't have any real helpful solutions for your issues. You could try the 1.0 LRS, which might require changes to your statements and digital books. You could give your server more resource, particularly more memory so that it can handle larger lists of statements. You could try getting the statements asynchronously and storing them locally.

tom

from adl_lrs.

Thanks and it was nice talking to you, now I'm going out but then you more story to share my experience with ADL_LRS.

Carlos.

from adl_lrs.