Bug #98640 Need a details about deprecation/removal PAD_CHAR_TO_FULL_LENGTH in sql_mode
Submitted: 18 Feb 2020 2:49 Modified: 18 Feb 2020 4:44
Reporter: Meiji Kimura Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Data Types Severity:S4 (Feature request)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any

[18 Feb 2020 2:49] Meiji Kimura
Description:
MySQL 8.0.x manual said about deprecation of PAD_CHAR_TO_FULL_LENGTH in sql_mode like this.

https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html#sqlmode_pad_char_to_full_length

Note: As of MySQL 8.0.13, PAD_CHAR_TO_FULL_LENGTH is deprecated. It will be removed in a future version of MySQL.

It's based on this WL.

WL#12129: Deprecate SQL_MODE PAD_CHAR_TO_FULL_LENGTH 
https://dev.mysql.com/worklog/task/?id=12129

As this WL said, we will be lost this behavior like ANSI specification after removal PAD_CHAR_TO_FULL_LENGTH in sql_mode. It's hard barrier for migration *from* legacy system with other database (Oracle, IBM Db2, SQL Server, Oracle, ....) so need detail description about it.

(1) Is there an alternative of PAD_CHAR_TO_FULL_LENGTH, or not ?
(2) If there is no alternative of PAD_CHAR_TO_FULL_LENGTH, need an explanation in advance widely before removal PAD_CHAR_TO_FULL_LENGTH.

How to repeat:
N/A

Suggested fix:
(1) Keep support for  PAD_CHAR_TO_FULL_LENGTH,or alternative method.
(2) Need more explanations on this manual. (e.g. need to modify application logic from other RDBMS's char()).

https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html#sqlmode_pad_char_to_full_length
[18 Feb 2020 4:44] MySQL Verification Team
Hello Meiji-San,

Thank you for the feature request!

regards,
Umesh