Fons,
> Well, I started with "I'm a beginner". But I'm sure there's no reason
> NOT to
> accept two records that are exactly the same. In the example I gave,
> it is clear
> that the information I want to store can contain two records that are
> exactly
> the same; doing the same thing, on the sa
The content of your record is not limited to user data. Including a field
that provides a unique key is simple: look at the documentation for data
type SERIAL for an easy way to do this.
You can also include information about when the record was inserted, and by
whom, just by including fields in
"Fons Rave" <[EMAIL PROTECTED]> wrote in message
9jbrpj$r67$[EMAIL PROTECTED]">news:9jbrpj$r67$[EMAIL PROTECTED]...
> > Well, there isn't an easy answer for you ... because you've designed
> > your database wrong. Records should *never* be the same. That is, ni
> > fact, one of the cardinal rule
> Well, there isn't an easy answer for you ... because you've designed
> your database wrong. Records should *never* be the same. That is, ni
> fact, one of the cardinal rules of Relational Database Design.
Well, I started with "I'm a beginner". But I'm sure there's no reason NOT to
accept two
If you include "oid" in your GROUP BY clause, you will get each distinct
record.
That will get you by for right now, but Josh's point is correct. You need
some kind of unique key in your table.
But... if you want to see every distinct record: why are you using a GROUP
BY?
> -Original Message
Fons Rave wrote:
>
> I'm writing a program in Delphi.
> In SQL I'm a beginner.
>
> I have a file in which there are records with what people have done. In the file
> are records with name, date, what they have done, time-length, etc. It is
> possible that there are two records that are exactly
