– from comment below:
One warning reviewing the code.
In case this ticket is implemented there are two occurrences of COALESCE..TO_NCHAR that must be taken care:
Hi , , can you please take a look at the pull request 207
I did tests and everything was running fine in the oracle with all the columns as VARCHAR2.
The ticket seems unnecessary now, but harmless to have it.
i has this issue guess reason by this ticket
because i apply some commit (not full) of this ticket i also hasn't test database to check update latest
can you confirm it's fixed on latest (in case it's issue by this ticket)?
I don't see that error in my DB - but seems there can be something wrong.
Reopening this ticket to investigate - there is probably something missing here - in my test database I see the columns SERNOCHARSOVERWRITE
are still NCHAR in the table M_ATTRIBUTESET
on my database LOTCHARSOVERWRITE, LOTCHAREOVERWRITE is changed
on code, only first commit of is apply, it hasn't migrate sql not sure what commit did that change