Expert? Certainly not me :) The question I will be waiting to see debated is whether you should "fabricate" an ID field (probably a counter), use ISBN or similar number, or use a compound key. FWIW, I invariably regret any decision I make in these areas, because there are tradeoffs. Relational databases are very good at what they do, which is storing tabular data and (most importantly) getting it back later; they are also a pain about it :( ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Alexandre Bergel [alexandre.bergel@me.com] Sent: Thursday, April 07, 2011 9:19 AM To: Pharo Development Subject: [Pharo-project] relational database and id field 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? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.