The 3 procedures Parse(Table|View|Routine)Structure() already do some connection specific stuff, and now even more, so they're moved to TMySQLConnection now. In order to display the right collation even if only the character set was found in a CREATE TABLE code, the default collation per charset is detected via CollationTable. See http://www.heidisql.com/forum.php?t=6348 .

This commit is contained in:
Ansgar Becker
2010-10-08 20:16:53 +00:00
parent 61855c4e8b
commit 5d13d0677b
9 changed files with 422 additions and 404 deletions

View File

@ -126,8 +126,8 @@ begin
FKeys.Clear;
FForeignKeys.Clear;
case FDBObj.NodeType of
lntTable: ParseTableStructure(FDBObj.CreateCode, FColumns, FKeys, FForeignKeys);
lntView: ParseViewStructure(FDBObj.CreateCode, FDBObj.Name, FColumns, Algorithm, CheckOption, SelectCode);
lntTable: FDBObj.Connection.ParseTableStructure(FDBObj.CreateCode, FColumns, FKeys, FForeignKeys);
lntView: FDBObj.Connection.ParseViewStructure(FDBObj.CreateCode, FDBObj.Name, FColumns, Algorithm, CheckOption, SelectCode);
else raise Exception.Create('Neither table nor view: '+FDBObj.Name);
end;