Project

General

Profile

Bug #5161

Upgrading from 1.8.8.4 to 1.9 hg of 2012-07-11 gives c_id messages

Added by Yannick Warnier almost 8 years ago. Updated almost 8 years ago.

Status:
Rejected - Abandoned
Priority:
Normal
Category:
-
Target version:
Start date:
11/07/2012
Due date:
% Done:

10%

Estimated time:
Spent time:
Complexity:
Normal
SCRUM pts - complexity:
?

Description

I'm attaching the HTML, result of the upgrade on my portal. I think there must be something wrong with the alert message now, as it seems to have appeared for each and everyone of the tables.


Files

upc.chamilocorp.com.html (202 KB) upc.chamilocorp.com.html Yannick Warnier, 11/07/2012 10:20

Associated revisions

Revision 045f144f (diff)
Added by Yannick Warnier almost 8 years ago

Added known issue - refs #5161

History

#1

Updated by Yannick Warnier almost 8 years ago

Mmmm... they continue to appear on my migrated portal.

I think the check code is wrong, because it appears even for the user table, which doesn't make sense:

Dev message: please add the c_id field in this query or report this error in support.chamilo.org
SELECT picture_uri FROM `upc_main`.`user` WHERE user_id=1

The rest of the tables already has the c_id (a quick look through seems to say so). The display_errors setting is off.

#2

Updated by Julio Montoya almost 8 years ago

  • Status changed from Assigned to Needs more info
  • Assignee changed from Julio Montoya to Yannick Warnier
  • % Done changed from 0 to 10

The problem here is that we search in the queries an string that contains something like "c_" for the new c_X tables. Your database name is something like "upc_" so that matchs that criteria. Those dev messages should be silently fired in the error_log before the stable released

#3

Updated by Yannick Warnier almost 8 years ago

  • Assignee changed from Yannick Warnier to Julio Montoya

That makes sense. Maybe check for c_ after the "." that represents the database name?

#4

Updated by Julio Montoya almost 8 years ago

  • Assignee changed from Julio Montoya to Yannick Warnier

Not possible to do that, I'm parsing the entire query not just the table name (problems appears when parsing queries with inner joins) I could move those dev messages to the function "Database::get_course_table()" but I'm not sure that every SQL query use that function

#5

Updated by Yannick Warnier almost 8 years ago

  • Status changed from Needs more info to Rejected - Abandoned

OK, no problem, we'll just add it as a "know issue".

Also available in: Atom PDF