• 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:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

when to throw DuplicateKeyException  RSS feed

 
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
in my create() of the interface, it throws DuplicateKeyException.
When should this be throw?
 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Depends. In my code: never.
=]
 
Ranch Hand
Posts: 78
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends the meaning you give to the record key.

One option is to consider the record key to be the record number. The
DuplicateKeyException is never thrown in that case (record numbers are all
differents).

Another option is to consider a subset of the record data as the key. For
example, contractor name + contractor location. But in that case, the update
method should throw the same exception.

This is really a matter of design choice.

Gilles
[ March 05, 2008: Message edited by: Gilles Marceau ]
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!