IdColumnReasons: Difference between revisions

Revision as of 08:43, 16 June 2011

Apache JMeter is a 100% pure Java desktop application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.

There's a place in Moodle Contrib for people to share their Jmeter scripts here: http://cvs.moodle.org/contrib/tools/jmeter/

For more information about JMeter and what it could help you to stress test your Moodle installation, please see: http://jakarta.apache.org/jmeter/

For JMeter FAQ, see: http://wiki.apache.org/jakarta-jmeter/JMeterFAQ

@@ Line 1: / Line 1: @@
-=Reasons=
+Apache JMeter  is a 100% pure Java desktop application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.
-There are was many "holy wars" about making additional surrogate key (id column) when "real" PK is can be combination of some FK in the table
-==first (not main) reason:==
+There's a place in Moodle Contrib for people to share their Jmeter scripts here:
-:But problems arrive when any of the get_record_XXX() functions are used, because all them returns associative arrays (GetAssoc()) where the first field in the returned recordset becomes the key of the array. So having those artificial "id" fields for each table is the only mechanism to fetch all the records from any table without losing some of them by the "key overwritten" effect. Following your example, something so simple like:
+http://cvs.moodle.org/contrib/tools/jmeter/
-:get_records('user_teachers')
+For more information about JMeter and what it could help you to stress test your Moodle installation, please see:
+http://jakarta.apache.org/jmeter/
-:won't work if the id field is missing. Only one occurrence of every teacher (the first field in the select, userid) will be returned, missing a lot of records.
+For JMeter FAQ, see:
+http://wiki.apache.org/jakarta-jmeter/JMeterFAQ
-:I'm pretty sure that we could bypass this limit in the long term (current recordsets implementation is a good start) but it would force us to review all the get_records_XXX() calls before, because a lot of them, simply will break and others could be using the GetAssoc() key feature in its own benefit so, modifying the type of arrays returned by the functions isn't an immediate alternative.
+==See also==
-(c) [http://moodle.org/user/view.php?id=3176 Eloy Lafuente (stronk7)]
+*[http://moodle.org/mod/forum/discuss.php?d=119443 Using Moodle forum discussion on Jmeter Scripts]
-==next reason (? - peoples, add more reasons!)==
+*[http://www.open.ac.uk/blogs/XHProf/?page_id=64 JMeter testplan generation Moodle plugin] developed by [http://moodle.org/user/view.php?id=264538&course=5 James Brisland]
-=See also=
+*[http://www.javapassion.com/handsonlabs/javatestjmeter/index.html JavaPassion LAB 1077: JMeter Load Testing]
-==Moodle links==
-* [http://moodle.org/mod/forum/discuss.php?d=38183 General developer forum » Important! insert_record() changes]
-* [http://moodle.org/bugs/bug.php?op=show&bugid=4583 Bug #4583 - hotpot doesn't restore]
-==External links==
-* [http://www.datawarehouse.com/article/?articleId=3103 Modeling Matters: The Semantics of Surrogate Keys and Business Keys, Part 1]
-* [http://www.datawarehouse.com/article/?articleId=3113 Modeling Matters: The Semantics of Surrogate Keys and Business Keys, Part 2]
-* [http://www.dbmsmag.com/9805d05.html Surrogate Keys: Keep control over record identifiers by generating new keys for the data warehouse]

Documentation

IdColumnReasons: Difference between revisions

Revision as of 08:43, 16 June 2011

See also