impact on MariaDB GUI and report design AFTER changing from Oracle

hi,

right now planning the last stage of oracle to mariaDB migration and here are some BI related question, hope you all can give a hand.

On the change on the DB and data column type. (e.g. Oracle varchar2() to MariadB varchar()),  usually any impact on GUI and report design?
LVL 1
marrowyungSenior Technical architecture (Data)Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nociSoftware EngineerCommented:
In general no.... as the underlying types can hold the same value.
In practice code that expects a float number (from a database) and nog receives an integer might have trouble if the code has not been adjusted.
(Numeric values are not passed as strings from database to frontend and vice versa) The GUI needs to be recompiled with the right drivers and the right schema.

Defaults may differ so leaning on heavy use of defaults may cause some work.
Date / Time formats and layouts may have those most changes. Those might require rework on queries to get an equal result.

Best is to try and walk through all screens. Let a regular user of the software do that they will spot differences a lot quicker.
marrowyungSenior Technical architecture (Data)Author Commented:
"In general no.... as the underlying types can hold the same value."

did you try similar migration before ? this is a big operation.

"In practice code that expects a float number (from a database) and nog receives an integer might have trouble if the code has not been adjusted."

sorry, what is nog  ? and what code has to adjust ?

"The GUI needs to be recompiled with the right drivers and the right schema."

you mean AFTER migration schema changed and that's why we need to recompile the BI tools ?

"Defaults may differ so leaning on heavy use of defaults may cause some work."

agree! so we need to redefine the default ?

" Let a regular user of the software do that they will spot differences a lot quicker."

this means setup the same BI tools on top of both DB and see the diff ?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Business Intelligence (BI)

From novice to tech pro — start learning today.