RE: Database collation
10-13-2014, 09:57 AM
(This post was last modified: 10-13-2014, 09:58 AM by sosojni.)
For example, file: https://github.com/sentora/sentora-core/...l_core.sql
Line 40:
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
That is source of all non UTF8's Almost all tables have it. It's basicly overriding general "database" collation.
That should be: CHARSET=utf8
When i change x_profiles table columns to UTF8 and than export x_profles, i get line:
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=3 ;
So i'm guessing is that we have to change every table charset. Database charset that is set up on line 13 will have effect only on new tables created after table is created on install.
Line 40:
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1;
That is source of all non UTF8's Almost all tables have it. It's basicly overriding general "database" collation.
That should be: CHARSET=utf8
When i change x_profiles table columns to UTF8 and than export x_profles, i get line:
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=3 ;
So i'm guessing is that we have to change every table charset. Database charset that is set up on line 13 will have effect only on new tables created after table is created on install.
