• Post Reply Bookmark Topic Watch Topic
  • New Topic

Can entity bean persistence be designed around views with triggers for i/u/d?  RSS feed

 
Marx Villegas
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Excuse my ignorance, I know it may be silly just to ask it, but, think about a complex db design with lots of foreign keys: you let your database make all the table joins and/or complicated data insert/update/delete logic (no one is going to do it faster than the db) and let your entity bean do the get/set job and db connection pooling easier for you.
Is it possible? Maybe it�s just a wild nonsense idea. Is it?
XM
 
Mark Spritzler
ranger
Sheriff
Posts: 17309
11
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, using Hibernate as an example, Hibernate prepares and creates CRUD statements in the beginning when a SessionFactory is created, you can turn this off, and you can also declare the crud statements to be used, which could be a call to a stored procedure, with a caveat. You can create the text of what the CRUD statement should be.

Mark
 
Marx Villegas
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sounds good Mark,
I'm not familiar with hibernate, I'll take a look at it so I understand what you're saying.
Thanks a lot!
XM
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!