• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

enity bean performance && commit options B/C

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi guys!

I really do need your experience.

If your app server isn't the only system accessing and possibly mutating certain tables in the database you have to choose commit options B/C.

Does anybody know how Oracle implements the task of ensuring the correct state of entity beans?

Are they really reloading the state from the database every time I access a getter?

Isn't this a really huge performance hit and is anyone able to provide something more concrete than 'huge'?

Do you know of some 'special tricks' Oracle AS does with Oracle DB?

Thank you very much for your help!

Best regards,
Juergen
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Please don't post the same question in multiple forums. Please post responses
here.
[ February 09, 2005: Message edited by: Jeanne Boyarsky ]
 
reply
    Bookmark Topic Watch Topic
  • New Topic