7.2 Custom Type Installation - NULL value database

Hello!

I've been trying to deploy custom types with attributes allowing NULL values to 7.2 environment and I'm facing weird issue at database end:

Here's the screenshot from the Composer where the attribute is set to have NULL values:

But at the database end, I don't see Allow NULLs checked:

I've tried with multiple Composer versions, but nothing works.

It's not recommended to make the changes directly on the database level as it might destroy views associated.

Any ideas or experiences on the same line?

Find more posts tagged with

Documentum

Comments

DCTM_Guru

Content Server maintains its on "data dictionary" that allow you to define the other values (ie cannot be blank, read-only, etc). I wouldnt worry about this too much at the database level.

FYI - make sure you run the data dictionary publishing job any time you changes to object types.

Raina

Hi Johnny

But when I'm trying to copy the database from 6.7 to 7.2 for upgrade, these tables which do not allow NULL are making issues. As such tables are not getting the data copy smoothly.

I tried to modify it the way its currently there with 6.7 environment, but the SQL Server Management Studio throws an error that all the views associations would be deleted. I'm not sure how this will effect.

fmejwagner

I think I have often seen a Documentum "NULL" value in string attributes as a single string (NULLSTRING constant).

That might cause different logic for "attr IS (NOT) NULL(string)" in DQL and in database level SQL...