ydb_env_set leaves gtm_prompt untouched #309
Description
Final Release Note
Description
Test case where the ydb_env_set file unsets gtm_prompt but does not unset ydb_prompt:
yottadbuser@yottadbworkshop:/tmp/tmp$ export gtm_prompt="XYZ> "
yottadbuser@yottadbworkshop:/tmp/tmp$ . /opt/yottadb/latest/ydb_env_set
yottadbuser@yottadbworkshop:/tmp/tmp$ echo $gtm_prompt
yottadbuser@yottadbworkshop:/tmp/tmp$ export ydb_prompt="XYZ> "
yottadbuser@yottadbworkshop:/tmp/tmp$ . /opt/yottadb/latest/ydb_env_set
yottadbuser@yottadbworkshop:/tmp/tmp$ echo $ydb_prompt
XYZ>
yottadbuser@yottadbworkshop:/tmp/tmp$ mumps -run %XCMD 'write $zyrelease,!'
YottaDB r1.22 Linux x86_64
yottadbuser@yottadbworkshop:/tmp/tmp$
Draft Release Note
When sourced, the ydb_env_set file does not clear the value of the environment variable gtm_prompt. Previously it did. The workaround was to use the ydb_prompt environment variable. As the gtm_prompt environment variable is deprecated, YottaDB recommends using ydb_prompt except in cases where compatibility with GT.M must be maintained. [#309]