| Anonymous | Login | Signup for a new account | 2010-02-09 09:57 EST |
| Main | My View | View Issues | Change Log | Roadmap | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0000955 | [Geeklog] Bugs | minor | always | 2009-08-28 07:15 | 2009-09-06 08:56 | ||
| Reporter | dhaun | View Status | public | ||||
| Assigned To | dhaun | ||||||
| Priority | normal | Resolution | fixed | ||||
| Status | resolved | Product Version | 1.6.0sr1 | ||||
| Summary | 0000955: SQL error in migration | ||||||
| Description |
I have an SQL dump that throws the following error when trying to import it using the install script's Migrate option: Notice: Error at the line 3005: SET character_set_client = @saved_cs_client;. Query: SET character_set_client = @saved_cs_client; MySQL: Variable 'character_set_client' can't be set to the value of 'NULL' |
||||||
| Additional Information |
The problem here is that bigdump imports 3000 lines at once. Line 3000 in this case is in the middle of the CREATE TABLE, so it adds the rest of the SQL statement until the ; and executes that. Then it starts importing the next portion, starting with the SET character_set_client = @saved_cs_client; in line 3005. However, "@saved_cs_client" is a variable that was only defined in the previous request but is unknown now. Hence the error ... This is actually an issue with bigdump. |
||||||
| Tags | install | ||||||
| Target | Next Release | ||||||
| Attached Files | |||||||
|
|
|||||||
| Copyright © 2000 - 2009 Mantis Group Hosted by pair.com |