Go to your local univeristy and pick up the CS curriculum's database text
book. (IFSM's may not be technical enough) In my class, our studies went
from the upper most level to statistically estimating the number of block
reads needed by a SQL statement.
I *think* it was called "Database Design Concepts" or something to that
effect. It had a blue cover with sailboats on it, IIRC. I'll check when I
get home. It covered both object and relational DBs, IIRC.
> -----Original Message-----
> From: pgsql-novice-owner@postgresql.org
> [mailto:pgsql-novice-owner@postgresql.org]On Behalf Of Josh Berkus
> Sent: Thursday, August 07, 2003 11:42 AM
> To: Jennifer Vargas; pgsql-novice@postgresql.org
> Subject: Re: [NOVICE] database design
>
>
> Jennifer,
>
> > What books or net sources are good for explaining the uses of features
> > like triggers,
> > stored procedures, transactions, and views in the *design* of a
> > database? I've seen
> > plenty of books at the store giving a functional overview of them, but
> > none of them
> > explain how, why, and when such features are integrated into a database
> > design.
>
> Frankly, I don't think there are any. The database application
> design books
> I've seen have focused on the app code and neglected the database beyond
> simple SQL. If anyone knows a book that's different, please let me know.
>
> In theory, I'm writing such a book, and so is one of the
> PostgreSQL sponsor
> companies. However, I don't think either of us has gotten past
> chapter 2 ...
>
> Me, I'll probably focus on magazine articles instead, I can get
> those done.
>
> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
