IdColumnReasons: Difference between revisions
From MoodleDocs
m (Fix small typo) |
m (headers and formatting) |
||
| Line 1: | Line 1: | ||
=Reasons= | |||
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 | 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:== | |||
: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: | |||
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: | |||
get_records('user_teachers') | :get_records('user_teachers') | ||
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. | :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. | ||
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. | :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. | ||
(c) [http://moodle.org/user/view.php?id=3176 Eloy Lafuente (stronk7)] | (c) [http://moodle.org/user/view.php?id=3176 Eloy Lafuente (stronk7)] | ||
==next reason (? - peoples, add more reasons!)== | |||
=See also= | |||
==Moodle links== | |||
links | |||
* [http://moodle.org/mod/forum/discuss.php?d=38183 General developer forum » Important! insert_record() changes] | * [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] | * [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=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.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] | * [http://www.dbmsmag.com/9805d05.html Surrogate Keys: Keep control over record identifiers by generating new keys for the data warehouse] | ||
Revision as of 19:50, 26 January 2006
Reasons
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:
- 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:
- get_records('user_teachers')
- 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.
- 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.
