Follow up at bottom:
On Tuesday 01 November 2005 04:15 pm, Hal Vaughan wrote:
> On Tuesday 01 November 2005 03:35 pm, [EMAIL PROTECTED] wrote:
> > Which tables can have duplicate records in them should be something
> > decided BEFORE you begin to populate the tables. 99.999% of the time,
> > each
On Tuesday 01 November 2005 03:35 pm, [EMAIL PROTECTED] wrote:
> Which tables can have duplicate records in them should be something
> decided BEFORE you begin to populate the tables. 99.999% of the time, each
> row of any one table should be different from every other row on the same
> table. Tha
Comments embedded. See below
Hal Vaughan <[EMAIL PROTECTED]> wrote on 11/01/2005 02:50:13 PM:
> I want to be sure I understand "INSERT IGNORE..." correctly before I
start
> depending on it. Up until now, I have not been using any kind of key or
> unique index, since many of my tables are cre
I want to be sure I understand "INSERT IGNORE..." correctly before I start
depending on it. Up until now, I have not been using any kind of key or
unique index, since many of my tables are created automatically and, until
now, it has been difficult for me to create a way to distinguish between
