List:General Discussion« Previous MessageNext Message »
From:Rolf Hopkins Date:July 13 2001 6:56am
Subject:INSERT INTO ... SET ...
View as plain text  
Hi all,

A week ago or so, someone on this list had a problem with inserting data.

I thought the reason was because they had mixed up the INSERT and UPDATE
statements.
ie.  INSERT INTO table_name SET column1=a_value, column2=a_value, ...

However, they said this statement works from the MySQL prompt.  I have just
found time to try this syntax today and I was amazed to find that it does
work in MySQL though it didn't work for Access.

In all the years I have worked/studied SQL, not once have I come across the
INSERT INTO ... SET ... syntax.
My questions are:

1. Is this a valid statement?
2. Is it ANSI standard?
3. Is this a MySQL feature / bug or do other DBs support this?
4. If it is valid, where is it documented?  All the SQL books that I've ever
come across, do not contain such a syntax.

Thread
INSERT INTO ... SET ...Rolf Hopkins13 Jul
  • Re: INSERT INTO ... SET ...John Birrell13 Jul
  • RE: INSERT INTO ... SET ...Jorge del Conde13 Jul
    • Re: INSERT INTO ... SET ...Rolf Hopkins13 Jul
    • Unsigned data with auto increment => Faster/better... ??David Bouw13 Jul
      • RE: Unsigned data with auto increment => Faster/better... ??Don Read13 Jul
  • RE: INSERT INTO ... SET ...Chris Bolt13 Jul
    • MyODBC 2.50.37 and Access 2000Kevin Smith13 Jul
      • Re: MyODBC 2.50.37 and Access 2000Joshua J. Kugler13 Jul
    • Re: MyODBC 2.50.37 and Access 2000Kevin Smith13 Jul
    • Re: MyODBC 2.50.37 and Access 2000Venu Anuganti13 Jul
      • Re: MyODBC 2.50.37 and Access 2000Sinisa Milivojevic14 Jul
    • Re: MyODBC 2.50.37 and Access 2000Kevin Smith13 Jul
      • Re: MyODBC 2.50.37 and Access 2000Dan Nelson14 Jul
RE: MyODBC 2.50.37 and Access 2000JHDrexler13 Jul
  • Re: MyODBC 2.50.37 and Access 2000Kevin Smith13 Jul
  • Re: MyODBC 2.50.37 and Access 2000Kevin Smith14 Jul