e: -
To: "Peter J Milanese" <[EMAIL PROTECTED]>
From: "STE-MARIE, ERIC" <[EMAIL PROTECTED]>
Date: 01/20/2004 02:41PM
cc: [EMAIL PROTECTED]
Subject: Re: Advice needed for high volume of inserts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On January 20, 2004 02:31
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On January 20, 2004 02:31 pm, Peter J Milanese wrote:
> It'll work.
>
> I do slight less on the way of inserts. What I do is dynamically generate
> the tables within my entry code, and merge tables based on the query. Good
> for large log parsers. Be
-Forwarded by Peter J Milanese/MHT/Nypl on 01/20/2004 02:36PM -
To: "STE-MARIE, ERIC" <[EMAIL PROTECTED]>
From: Peter J Milanese/MHT/Nypl
Date: 01/20/2004 02:31PM
cc: [EMAIL PROTECTED]
Subject: Re: Advice needed for high volume of inserts
It'll work.
I do slig
Message-
From: clay bond [mailto:[EMAIL PROTECTED]]
Sent: Saturday, May 19, 2001 6:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Advice needed
On Sat, 19 May 2001, Dave Carter wrote:
> I'm converting an Access db to mySQL, and Access allows users to Insert
> Records into a table AN
On 19-May-01 Dave Carter wrote:
> I'm converting an Access db to mySQL, and Access allows users to Insert
> Records into a table AND call them as well in the FROM clause. This is
> illeagal in ANSI SQL however and therefore illeagal in mySQL, but I don't
> know really how to get around it. How ca
On Sat, 19 May 2001, Dave Carter wrote:
> I'm converting an Access db to mySQL, and Access allows users to Insert
> Records into a table AND call them as well in the FROM clause. This is
> illeagal in ANSI SQL however and therefore illeagal in mySQL, but I don't
> know really how to get around
Hi!
It;s been a while since i used Access, so i can't remember exactly
what you mean. But for what you've said you probably have three
choises:
1) Create a primary key, try to insert a record with already
existing
key and fail. Failure means that record already exists. Nothing
special.
2)
