You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[1.0.1] remove whitespace and commented out old code on all stored programs
@@ -115,4 +116,8 @@
115
116
-[3.2.5] modify TABLE `import_load` added six columns for process execution durations in seconds.
116
117
-[3.2.5] modify `logs2mysql.py` reworked all process message logging verbiage to provide child process summary information at each phase. Running log generator stress tests flushed this out.
117
118
-[3.2.5] modify `logs2mysql.py` reduced number of cursor objects created by reusing only two cursor objects. Reduced all variables for import_file TABLE processing using same variables for all.
118
-
-[3.2.5] modify TABLES `access_log_useragent` and `log_client` added indexes for use in `logs2mysql.py` processing.
119
+
-[3.2.5] modify TABLES `access_log_useragent` and `log_client` added indexes for use in `logs2mysql.py` processing.
120
+
-[3.2.6] created new Python script to generate `apache_logs_schema.sql` from the 25 refined development source code scripts. Prior to this version file was generated by MySQL Workbench.
121
+
-[3.2.6] repository had MySQL Workbench generated script that added CHARSET and COLLAT. The raw source code scripts did not specify CHARSET or COLLATE. Raw source code scripts worked fine on MySQL and MariaDB testing.
122
+
-[3.2.6] MySQL 9.1 default is CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci. MariaDB 11.6 default is CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci. COLLATE=utf8mb4_0900_ai_ci does not exist in MariaDB causing script errors.
123
+
-[3.2.6] The solution that works for both MySQL and MariaDB is only specify CHARSET=utf8mb4. If CHARACTER SET charset_name is specified without COLLATE, character set charset_name and its default collation are used.
0 commit comments