- This topic has 11 replies, 3 voices, and was last updated 17 years ago by
.
-
Posts
-
It is indicating that the specified table in the entity doesn’t exist when I know it does.
Hmm… so the entities are using the correct PU from the persistence.xml file BUT the query itself is failing saying the table doesn’t exist?
Thanks for your help. Also ICEFaces is awesome. I switched from GWT. It is exactly what I needed.
That’s great news, I’ll let the team know!
@support-rkalla wrote:
It is indicating that the specified table in the entity doesn’t exist when I know it does.
Hmm… so the entities are using the correct PU from the persistence.xml file BUT the query itself is failing saying the table doesn’t exist?
The entities are using the proper PU but there are about 25 other tables that have a relationship with the tables that I am using in my application and I don’t need these other tables. I think is what is causing the “table not found” issue. I would have to create classes and entities for all these other tables eventhough I am not using them. In this respect I think JPA needs more work.
The JPA would need some kind special entity that could identify these other tables (constraints) without needing to create classes for all of them in the application. This way the tables could reference them in the rdbms as require to maintain the relationship.
Thanks for your help. Also ICEFaces is awesome. I switched from GWT. It is exactly what I needed.
That’s great news, I’ll let the team know!
