On Thu, Apr 7, 2011 at 2:39 PM, laurent laffont <laurent.laffont@gmail.com> wrote:

On Thu, Apr 7, 2011 at 3:19 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Hi!

Since there are some experts in databases here, I ask a general question about it.
Assume that I have to use a relational database to store, let's stay instances of Stef's ComicBook class.
Should the class ComicBook have a field id to uniquely identify a book?

I always put an id field. All cases without id I've encountered were always a pain.

I don't have any argument against unique id.��

And if you are thinking about ISBN:

- ISBN "should" be unique. In reality they're not. Because we communicate with software that have bugs. People who enter ISBN have bugs too. And when you mashup datas you always get soon or later 2 different documents with same ISBN.

- documents edited before 1972 and not reedited after don't have ISBN.

Laurent.

��

Laurent.

��

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel ��http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.