Win a copy of TDD for a Shopping Website LiveProject this week in the Testing 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:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Sybex 816 (Kindle) Chapter 10., Table 10.4., p. 831-834

 
Ranch Hand
Posts: 34
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In the table like in the subject, which lists some of the PreparedStatement methods, in the second column are:

Boolean, Double, Int, Long, Object, String


If we keep the Wrapper Classes, it could be (Int --> Integer):

Boolean, Double, Integer, Long, Object, String.


Or maybe it would be better to replace the Wrapper Classes types with their primitive counterparts?

boolean, double, int, long, Object, String


According to the docs the setX() methods do not have the overloads taking the Wrapper Classes as the 2nd parameter.
 
author & internet detective
Posts: 41073
848
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
Yes. The primitive classes would have been better here! Added to the errata.
 
Popeye has his spinach. I have this tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
    Bookmark Topic Watch Topic
  • New Topic