Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am using hibernate in the persistance layer in a Maven project and I’m really new to this. Sometimes, when performing read operations from the database through jpa/hibernate some of the tables are dropped. The project doesn’t implement that kind of functionality. Is this a known issue? The actions are only read actions.
Now I finally found the answer. Seems like some config in the integration tests made them run against wrong db(the one where the tables were dropped), not the im-db we wanted to use. And the integration tests are supposed to do a drop, but then no new tables could be created. So the answer to this question is loosley coupled to the problem but rather to our incorrect configuration. but maybe this answer can make other’s having the same problem think twice about this.