Debug info: Unknown column 'a.question' in 'on clause'
SELECT qa.*, q.qtype
FROM mdl_question_answers qa
JOIN mdl_question q ON a.question = q.id
[array (
)]
Stack trace:
* line 391 of /lib/dml/moodle_database.php: dml_read_exception thrown
* line 691 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
* line 5068 of /lib/db/upgrade.php: call to mysqli_native_moodle_database->get_recordset_sql()
* line 1309 of /lib/upgradelib.php: call to xmldb_main_upgrade()
* line 264 of /admin/index.php: call to upgrade_core()
SNAP!!! But I think it's now being dealt with...hopefully!!!
Debug info: Unknown column 'a.question' in 'on clause'
SELECT qa.*, q.qtype
FROM mdl_question_answers qa
JOIN mdl_question q ON a.question = q.id
[array (
)]
Stack trace:
* line 391 of /lib/dml/moodle_database.php: dml_read_exception thrown
* line 691 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
* line 5068 of /lib/db/upgrade.php: call to mysqli_native_moodle_database->get_recordset_sql()
* line 1309 of /lib/upgradelib.php: call to xmldb_main_upgrade()
* line 264 of /admin/index.php: call to upgrade_core()
I had the exact same error on my instance.
Although RC1 news said "From now on, though, you can rely on the upgrade path from day to day." - It still was and is a development release. If such upgrades go wrong with these releases, we can't blame the developers.
If you upgraded regularly through cvs or git like me, you were not affected. - But that doesn't mean, that the DB on my testserver is absolutely clean. I'll better drop the tables after final release. I hope end of November / December will be it
Not that I think it's a big deal (small coding errors will always happen, I've certainly made plenty) but this code is to deal with people upgrading from 1.9 which is about to be quite a lot of people. Never mind those testing the upgrade (which you should, of course) to make sure it works.
I didn't think anybody was blaming anyone
I didn't think anybody was blaming anyone
Sure, you are right, RC1 -> RC2 upgrades might not be guaranteed / tested to work but upgrades from 1.9.x really have to work.
Same here, I tried 1.95+ to 2.0 RC2 latest build upgrade. Earlier, this issue was not there with RC1.
After clicking to continue, I got this:
Notice: Undefined property: object::$format in /moodle/blocks/html/block_html.php on line 61
Error reading from database
Debug info: Unknown column 'display' in 'field list'
SELECT id, name, display, displayoptions, tobemigrated, revision FROM mdl_resource WHERE id = ?
[array (
0 => '250',
)]
SELECT id, name, display, displayoptions, tobemigrated, revision FROM mdl_resource WHERE id = ?
[array (
0 => '250',
)]
Stack trace:
- line 391 of /lib/dml/moodle_database.php: dml_read_exception thrown
- line 732 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
- line 1243 of /lib/dml/moodle_database.php: call to mysqli_native_moodle_database->get_records_sql()
- line 1215 of /lib/dml/moodle_database.php: call to moodle_database->get_record_sql()
- line 1195 of /lib/dml/moodle_database.php: call to moodle_database->get_record_select()
- line 236 of /mod/resource/lib.php: call to moodle_database->get_record()
- line 1100 of /course/lib.php: call to resource_get_coursemodule_info()
- line 1738 of /course/lib.php: call to get_array_of_activities()
- line 3042 of /lib/moodlelib.php: call to rebuild_course_cache()
- line 32 of /blocks/site_main_menu/block_site_main_menu.php: call to get_fast_modinfo()
- line 689 of /blocks/moodleblock.class.php: call to block_site_main_menu->get_content()
- line 232 of /blocks/moodleblock.class.php: call to block_list->formatted_contents()
- line 882 of /lib/blocklib.php: call to block_base->get_content_for_output()
- line 934 of /lib/blocklib.php: call to block_manager->create_block_contents()
- line 342 of /lib/blocklib.php: call to block_manager->ensure_content_created()
- line 4 of /theme/base/layout/frontpage.php: call to block_manager->region_has_content()
- line 627 of /lib/outputrenderers.php: call to include()
- line 585 of /lib/outputrenderers.php: call to core_renderer->render_page_layout()
- line 1132 of /lib/setuplib.php: call to core_renderer->header()
- line ? of unknownfile: call to bootstrap_renderer->__call()
- line 89 of /index.php: call to bootstrap_renderer->header()
That's a different problem 