I have been working with Documentum 7.3.0190.0080 backed by PostgreSQL 9.4.
The whole time I thought that it's normal that Documentum truncates trailing spaces in string attributes during selection. I mean, when you save an object, the trailing spaces are saved in the SQL database (which can be seen if you concat the values with SQL), but when you fetch and call getString() the spaces are gone.
Then I moved to Oracle 11 and Documentum 7.3.0070.0047 and found that it preserves the trailing spaces.
I'm using the same client (a Java program or sometimes DQMan) to connect to both content servers.
So what is it? Does Documentum always trim the values if it's configured for PostgreSQL? Is it configurable?
create TYPE mytype ( s string(50) ) supertype dm_sysobject publish;
create mytype object link '/Temp', set s = 'abc ';
execute exec_select_sql with query = 'select ''['' || s || '']'' as s from mytype_s';
-- result on all envs: [abc ]
select s from mytype;
-- result on Oracle: 'abc '
-- result on PostgreSQL: 'abc'
