• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

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

 
Ranch Hand
Posts: 34
5
  • Mark post as helpful
  • send pies
  • 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: 40354
819
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes. The primitive classes would have been better here! Added to the errata.
reply
    Bookmark Topic Watch Topic
  • New Topic