This week's book giveaway is in the Other Languages forum.
We're giving away four copies of Rust Web Development and have Bastian Gruber on-line!
See this thread for details.
Win a copy of Rust Web Development this week in the Other Languages forum!
  • 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

Statement, PreparedStatement, CallableStatement

 
Ranch Hand
Posts: 1608
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The inheritance hierarchy for JDBC statements puzzles me a little.
Specifically, why would PreparedStatement and CallableStatement want to inherit some of the methods of Statement?

For example, I tried the following:


I tried code similar to the above with MS SQL Server 2000 driver, only to be given an exception.
Why does the JDBC API allow this behaviour?
Is there ever a reason why you'd do such a thing?
Is it a fair statement that some of the Statement methods should never be called on a PreparedStatement (and CallableStatement) instance?

Advice is most appreciated.
reply
    Bookmark Topic Watch Topic
  • New Topic