[TYPO3] utf-8 - setDBinit doesn't solve everything (eg. charset of tables created by 'compare databse' tool)

[Amiran Chyb]

On Fri, 16 Mar 2007 13:57:08 +0100, Amiran Chyb  
<amiran.chyb at stopspam.gmail.com> wrote:

> Hi there
>
>
> I've just switched to full utf-8 model (including db). BTW I had to  
> apply patch to base64-encode cache hashes to prevent the "No template  
> found!" error (see:  
> http://bugs.typo3.org/print_bug_page.php?bug_id=0005088).
>
>
> But to the point:
>
> I've added the following to setDBinit:
> SET CHARACTER SET utf8;
> SET NAMES utf8;
> SET SESSION character_set_server=utf8;
>
> but nevertheless, running COMPARE DATABASE tool from install tool  
> creates all tables and columns with latin1 charset (which is  
> server-default - I can't change that, and usually one cannot). Is it a  
> problem of a compare database tool not using the setdbinit commands, or  
> maybe all new tables creation in typo3 won't be affected by setDBinit  
> settings (even if the commands are fired at the beginning of a  
> connection) and will have default charset set?
> If so, then maybe there's another mysql session variable responsible for  
> default charset of created tables?



I've checked - new tables created by Typo (not by COMPARE tool but eg. by  
adding new ext) have their charset set correctly as in setDBinit settings.  
So is it the problem of Comparet Tool not using typo3 db api.


Am