to assignments belonging to one exact course. if not specified all
assignments in site are checked (old approach).
This function in used by restore_refresh_events() to recalculate module events.
Perhaps it should become a standard function in NEWMODULE to allow new modules
implement it.
Ciao :-)
1) There is a new site-wide configuration variable called maxbytes,
which provides an upper filesize limit for all (student) uploads.
2) There is a new course-level variable called maxbytes, which further
limits uploads within a course.
3) There is a new maxbytes field for forums, which further restricts
the size allowed in a particular forum. There is also a new config
variable in the module configuration to specify a default size
to use when defining a new forum.
4) Assignments already had a limit, but this is now aware of the other
limits, and like forums there is now a settable default value.
5) Finally, the sizes of files (Gb, Mb, Kb, bytes) is now translatable
in the language packs.
still producing too much data and overflowing PHP memory on busier
sites (eg moodle.org).
Now, there are more database queries, which is unfortunate, but the
data is much more specific, and no sorting needs to be done, so
this is a performance boost.
I don't know how these will cancel out ... my guess is that very
small sites may be very slightly slower on the course page, but
that large sites will be much faster.
Let's see.
Moved COURSE_TEACHER_COLOR out to style sheets where it belongs (.teacheronly)
Added some efficiency when printing recent activity
- don't print more than one weeks worth of updates
- don't keep re-parsing logs once they've been used
Moodle tables.
ie user -> userid in many tables, plus in user_students
start -> starttime and end -> endtime
I've just done all this as carefully as I could ... I don't think
I missed anything but it's pretty intensive work and I'd be fooling myself
if I didn't think I'd missed a couple.
Note that this version should pretty much be able to bootstrap itself
using PostgreSQL now ... but this is untested
Basically all the Database functions are in lib/datalib.php
and the web functions are all in lib/weblib.php, so
moodlelib.php is much thinner than it was.
Data functions have been extended ... most old calls will
still work, but now many more SQL commands can be performed
using the datalib functions rather than using SQL. I'm
currently moving through the whole tree replacing SQL
calls or at least concentrating them in one section of
mod/xxx/lib.php
Still working on forums, quizzes, surveys, resources.
The tree is currently not full working ... some things are
half-completed ... will resume tomorrow.
