"[EMAIL PROTECTED] (Tom Lane)" wrote in comp.databases.postgresql.docs:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> I feel that there is a very useful dividing line between chapters 2 and
>> 3: chapter 2 is about getting the data in and out, to give beginners a
>> feeling that the database
2. The SQL Language
2.1. Introduction
2.2. Concepts
2.3. Creating a New Table
2.4. Populating a Table With Rows
2.5. Querying a Table
2.6. Joins Between Tables
2.7. Aggregate Functions
2.8. Updates
2.9. Deletions
3. Advanced Features
3.1. Introduction
3.
On Sun, 11 Jan 2004, Bret Busby wrote:
>
> As a person who is not a PostgreSQL guru or a database guru, or who
> has worked on databases with the numbers of tables in the hundreds
> or thousands, but, a person with (relatively) basic database skills, and
> who knows of relational database desi
On Thu, 8 Jan 2004, David Fetter wrote:
>
> Christopher Browne <[EMAIL PROTECTED]> wrote:
> > Oops! [EMAIL PROTECTED] (David Fetter) was seen spray-painting on a wall:
> >> On Thu, Jan 08, 2004 at 06:07:13PM +0100, Peter Eisentraut wrote:
> >>> David Fetter wrote:
> >>> > Expanding on that, putti
On Thursday 08 January 2004 22:44, Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > I feel that there is a very useful dividing line between chapters 2 and
> > 3: chapter 2 is about getting the data in and out, to give beginners a
> > feeling that the database system is working, c
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (Bruce
Momjian) transmitted:
> David Fetter wrote:
>> Kind people,
>>
>> I was looking over the Tutorial section, and noticed that Foreign Keys
>> is in the "Advanced" section. I believe this is a mistake, and would
>> like
Clinging to sanity, [EMAIL PROTECTED] (David Fetter) mumbled into her beard:
> Chris Browne, could you give me a pointer to your patch so we don't
> step on each other's feet?
It was posted on the patches list on 2003-12-29...
--
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','cbbrowne.com'
Oops! [EMAIL PROTECTED] (David Fetter) was seen spray-painting on a wall:
> On Thu, Jan 08, 2004 at 06:07:13PM +0100, Peter Eisentraut wrote:
>> David Fetter wrote:
>> > Expanding on that, putting FK's in "Advanced Features" gives the
>> > (IME always wrong) impression that they're optional.
>>
>>
Christopher Browne <[EMAIL PROTECTED]> wrote:
> Oops! [EMAIL PROTECTED] (David Fetter) was seen spray-painting on a wall:
>> On Thu, Jan 08, 2004 at 06:07:13PM +0100, Peter Eisentraut wrote:
>>> David Fetter wrote:
>>> > Expanding on that, putting FK's in "Advanced Features" gives the
>>> > (IME al
On Thu, Jan 08, 2004 at 06:07:13PM +0100, Peter Eisentraut wrote:
> David Fetter wrote:
> > Expanding on that, putting FK's in "Advanced Features" gives the
> > (IME always wrong) impression that they're optional.
>
> They *are* optional.
I disagree.
> The first chapter is about getting the data
Peter Eisentraut wrote:
Jeroen Ruigrok/asmodai wrote:
Because foreign keys are part of database design 101?
Indeed, but the subject matter of chapter 2 of the tutorial is more like
introduction to databases 099. Others may rightfully claim that
transactions and views
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I feel that there is a very useful dividing line between chapters 2 and
> 3: chapter 2 is about getting the data in and out, to give beginners a
> feeling that the database system is working, chapter 3 is about
> refining the data structures for hig
On Thu, 2004-01-08 at 12:07, Peter Eisentraut wrote:
> David Fetter wrote:
> > Expanding on that, putting FK's in "Advanced Features" gives the (IME
> > always wrong) impression that they're optional.
>
> They *are* optional.
>
> The first chapter is about getting the data in and out. That is no
Jeroen Ruigrok/asmodai wrote:
> Because foreign keys are part of database design 101?
Indeed, but the subject matter of chapter 2 of the tutorial is more like
introduction to databases 099. Others may rightfully claim that
transactions and views are also elementary parts of database
applicatio
David Fetter wrote:
> Expanding on that, putting FK's in "Advanced Features" gives the (IME
> always wrong) impression that they're optional.
They *are* optional.
The first chapter is about getting the data in and out. That is not
optional for using a database. Transactions, views, foreign key
On Thu, Jan 08, 2004 at 08:52:29AM +0100, Jeroen Ruigrok/asmodai wrote:
> -On [20040108 07:32], Peter Eisentraut ([EMAIL PROTECTED]) wrote:
> >Why?
> Because foreign keys are part of database design 101?
Yes.
Expanding on that, putting FK's in "Advanced Features" gives the (IME
always wrong) im
-On [20040108 07:32], Peter Eisentraut ([EMAIL PROTECTED]) wrote:
>Why?
Because foreign keys are part of database design 101?
--
Jeroen Ruigrok van der Werven / asmodai / kita no mono
PGP fingerprint: 2D92 980E 45FE 2C28 9DB7 9D88 97E6 839B 2EAC 625B
http://www.tendra.org/ | http://diary.in-
David Fetter wrote:
> I was looking over the Tutorial section, and noticed that Foreign
> Keys is in the "Advanced" section. I believe this is a mistake,
Why?
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Wed, Jan 07, 2004 at 09:13:47PM -0500, Bruce Momjian wrote:
> David Fetter wrote:
> > Kind people,
> >
> > I was looking over the Tutorial section, and noticed that Foreign
> > Keys is in the "Advanced" section. I believe this is a mistake,
> > and would like to patch up the difference. What
David Fetter wrote:
> Kind people,
>
> I was looking over the Tutorial section, and noticed that Foreign Keys
> is in the "Advanced" section. I believe this is a mistake, and would
> like to patch up the difference. What files are involved in the
> source tree apart from doc/src/sgml/query.sgml
Kind people,
I was looking over the Tutorial section, and noticed that Foreign Keys
is in the "Advanced" section. I believe this is a mistake, and would
like to patch up the difference. What files are involved in the
source tree apart from doc/src/sgml/query.sgml and
doc/src/sgml/query.sgml ?
T
21 matches
Mail list logo
