In-memory DB translation feature

[gopalramadugu]

• Description of problem
  One of the best practices of Obevo describes about using in-memory translation feature.
  We use oracle as our database. We would like to see if there a way to use this feature if it is possible (I thought this was specific to Hibernate). How does Obevo tests oracle changes ? We would like to know if there any other ways to test code locally before we deploy our code to a standalone environment. I see you use virtual box wanted to see if this is still the best way to test code or if there are other means ?

[shantstepanian]

Hi, the in-memory database testing is limited to tables/views/static data (i.e. notably not including objects that execute logic, such as functions or stored procedures). If you are fine with that, then the in-memory solution could potentially be built out. Though it is mainly targeted for Java applications

Otherwise, you can also try the Docker setup.
(I had started w/ the Docker setup originally; I switched to Virtualbox because I had issues w/ Docker, but it was actually something on my side. I've since switched back to Docker)
The oracle-docker-setup.sh, oracle-init.sql, and local-oracle-creds.yaml files inside obey-db-oracle should get you started on that. Also see the Oracle Docker page here - https://hub.docker.com/_/oracle-database-enterprise-edition

If the docker testing works for you, then we can lower the priority on the in-memory work. Let me know what you think