What do you think?
Rate this book
The Set Model for Database and Information Systems
An innovative, even radical, approach to database modeling which could prove to be as seminal as Codd's work on the relational model. Russian computer scientists have been hampered by old, slow systems and by a lack of memory and storage capacity; the result, as demonstrated here, is unconventional thinking that maximizes resources and produces "elegant," compact programs.
Paperback
First published July 1, 1994
1 person want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 of 1 review
January 24, 2008
Mikhail M. Gilula, The Set Model for Database and Information Systems (Addison-Wesley, 1994)
Gilula, at one point in this book, says "As far as possible, we have attempted to simplify the presentation in order to make it intelligible to readers who have had no special training in the field of mathematical logic." Could have fooled me. It's possible for the bachelor's earner to grasp, but just barely and after multiple readings. You're probably better off not trying to tackle this one unless your bachelor's is in math, or you've earned an advanced degree.
That said, is there really any reason to tackle it at all? A number of websearches on set theory as it applies to current database technology (and specifically Starset, the language proposed and outlined herein) turns up precious little, leading this reviewer to believe that the relational model, which is what Gilula and co. are trying to overthrow, has won this battle without too much effort. This book is, at this point in time, going to appeal at most to a niche market. Gilula mentions that the original Starset interpreters were written in C, and the appendix has more than enough info for the hobbyist or vertical-market software developer to reverse-engineer Starset and program a home version of it. And Gilula certainly does make an interesting case for set-model databases, and he does so with just enough clarity to make the average DBA wonder if, perhaps, a set-model database might be of more use than a relational database for any given purpose. However, unless that DBA has unlimited time and resources, this is probably going to remain no more than an interesting artifact. **
Gilula, at one point in this book, says "As far as possible, we have attempted to simplify the presentation in order to make it intelligible to readers who have had no special training in the field of mathematical logic." Could have fooled me. It's possible for the bachelor's earner to grasp, but just barely and after multiple readings. You're probably better off not trying to tackle this one unless your bachelor's is in math, or you've earned an advanced degree.
That said, is there really any reason to tackle it at all? A number of websearches on set theory as it applies to current database technology (and specifically Starset, the language proposed and outlined herein) turns up precious little, leading this reviewer to believe that the relational model, which is what Gilula and co. are trying to overthrow, has won this battle without too much effort. This book is, at this point in time, going to appeal at most to a niche market. Gilula mentions that the original Starset interpreters were written in C, and the appendix has more than enough info for the hobbyist or vertical-market software developer to reverse-engineer Starset and program a home version of it. And Gilula certainly does make an interesting case for set-model databases, and he does so with just enough clarity to make the average DBA wonder if, perhaps, a set-model database might be of more use than a relational database for any given purpose. However, unless that DBA has unlimited time and resources, this is probably going to remain no more than an interesting artifact. **
Displaying 1 of 1 review