Side Effects and Breaking Changes in OutSystems 11 - Database - Oracle

I have a question regarding the following breaking change:



Issue: Publishing an eSpace with a text entity attribute whose length is longer than 2000 characters but for which the metamodel says its length is exactly 2000 characters causes an error in Oracle, stating that the column's underlying data type cannot be changed.

Question: This is only applied to Outsystems Platforms that use Oracle as native, right? Or also if the we use Oracle as External Database? 

This doesn't seems very clear to me on Side Effects and Breaking Changes in OutSystems 11, but it seems so.


Yes, only for the OS database itself, not for external databases (as you couldn't publish an eSpace/Module that affects it).


Ok. Thanks Kilian.

You're most welcome. Could you mark my answer as Solution? Thanks.