There is (in my assignment at least) no key defined so you can never get a DuplicateKeyException.
It is however conceivable that another database format might have a defined key, so the interface supports the option to throw that exception. That's often the case with interfaces you get from 3rd parties, they're more generic than you have a need for because you're not the only one coding against them.
I defined my own composite primary key from the data in my db file, so for me the DuplicateKeyException was actually usable. I realise this is technically outside the scope of the project; I just have a pet hatred for duplicate data
McFinnigan? Never heard of him. Nobody here but us chickens...<br /> <br />SCJP for Java 1.4<br />SCJD for Java 5.0
Joined: Aug 25, 2006
Cheers for the advice. Documenting it sounds like the way to go...