Judy Hsu による投稿

Moodle in English -> General developer forum -> Databases: What tables tend to get big and require (manually) creating proper indexes? -> Re: Databases: What tables tend to get big and require (manually) creating proper indexes?

- Judy Hsu の投稿

Hi Samuli, are you sure you meant the "info" column on the "log" table?? I sampled some content of the "info" column of the log table, but I'm not sure whether it is suitable for indexing... We have created indexes for all the other columns for the log table, but just not the "info" column...

thanks!

評点平均: -

Moodle in English -> General developer forum -> Databases: What tables tend to get big and require (manually) creating proper indexes?

- Judy Hsu の投稿

Hi all, just a quick question, for larger institute which has a big database (say, serving 10000+ students and 1000+ faculty members), which table(s) tend to get really BIG over time, and by default moodle installation did not create any index?? It seems that on our server some queries (read operations) tend to be very slow, so I don't know if we should start investigating what tables need to be properly indexed so that we could increase the performance?? We are running Moodle 1.5.2 right now.. thanks!

評点平均: -

Moodle in English -> Wiki -> wiki view.php v1.44 (moodle 1.5.2) and v1.49 (moodle 1.6 beta) patch question

- Judy Hsu の投稿

Hi all:

We have moodle 1.5.2 installed on our pilot testing server and we found a error with the wiki (/mod/wiki/view.php version 1.44). If you edit a new wiki page and then save it, then re-edit it and delete all the content, it will show you this error message:

---begin of error message---

Try not to worry too much about formatting, it can always be improved later.

var config = new HTMLArea.Config(); config.pageStyle = "body { background-color: #ffffff; font-family: Trebuchet MS,Verdana,Arial,Helvetica,sans-serif; }"; config.killWordOnPaste = true; config.fontname = { "Trebuchet": 'Trebuchet MS,Verdana,Arial,Helvetica,sans-serif', "Arial": 'arial,helvetica,sans-serif', "Courier New": 'courier new,courier,monospace', "Georgia": 'georgia,times new roman,times,serif', "Tahoma": 'tahoma,arial,helvetica,sans-serif', "Times New Roman": 'times new roman,times,serif', "Verdana": 'verdana,arial,helvetica,sans-serif', "Impact": 'impact', "Wingdings": 'wingdings'}; function spellClickHandler(editor, buttonId) { editor._textArea.value = editor.getHTML(); var speller = new spellChecker( editor._textArea ); speller.popUpUrl = "http://xxx.../lib/speller/spellchecker.html"; speller.spellCheckScript = "http://xxx.../lib/speller/server-scripts/spellchecker.php"; speller._moogle_edit=1; speller._editor=editor; speller.openChecker(); } HTMLArea.replace('edit-content', config);

---end of error message---

I then tested the moodle 1.6 beta (came with /mod/wiki/view.php version 1.49) and it actually works fine without any error message, so my question is:

1. Should I just do a hand patch to replace the view.php on our testing server and upgrade this script to version 1.49?? Would this totally fix the problem?

2. What would be the best way to do the upgrade/patch?? I was thinking of doing a side-by-side comparison and then "hand patch" it, but I hope there is a better way of doing the patch... (we haven't install CVS or Subversion yet)...

Thanks!

評点平均:Useful (1)