MSD - problem

[gtbu]

1. When importing a big 1.2GB sql-database without splitting, it finally got the error :

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; -> Variable 'character_set_client' can't be set to the value of 'NULL'.

though this line (and 2 others) is outcommented in the database /* ....*/

2. While splitting i miss the possibility to choose UTF8 instead of latin - i need hebrew and chinese and japanese letters . Is there an entry (here the error does not come up) in some file which solves that ?

[r23]

hello and welcome

When importing a big 1.2GB sql-database without splitting, it finally got the error :

MyOOS Dumper does not import data. Via File Administration you can upload SQL files.

8<--
Maximum file size: XY
If your Dumpfile is bigger than the above mentioned limit, you must upload it via FTP into the directory "work/backup". After that you can choose it to begin a restore progress.
8<--

With MyOOS Dumper you can restore your database. But first you should backup your database with this tool. Unfortunately, there is no import of foreign data sources. Then you can use at most the converter.

to point 2

MyOOS dumper stores all possible MySQL charsets in $config['mysql_standard_charset']

with the get_sql_encodings function, myOOS Dumper recognizes the fonts on the system.

~/inc/functions_global.php (2 hits)
Line 1191: function get_sql_encodings()

[gtbu]

I have of course loaded the big database into the backup-directory ..!

1. My first problem was, that the database file was generated with phpmyadmin 4.9.1 which adds
   /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; (and 2 similar other lines from about line 10 of the sql-file.
   The error -> Variable 'character_set_client' can't be set to the value of 'NULL'. --- comes first at the very end, when the database has already been imported - > may be there is a second control run..? The 3 lines are in the header and not in the end (controlled with dbforge studio express)

2. The latin instead utf8 comes during the conversion into 32 files (of course i have chosen twice UTF8 as in the picture) . It is not encoding of the UTF8 file....but breaking into peaces - a different code...

(The result of an imported (Xampp,php7.1) splitted database of 1.2 GB is, that several pages are missing.
If i make a direct import in Xampp then these pages are there and the imported database is 80 KB bigger ) - thats why i opened this issue).
I cant import such a huge database at my provider - but in the imported splitted i have missing pages.

P.S. $config['mysql_standard_charset'] is not predefined in the config.php