here? What would be the correct way to design this db?
Thanks for the help.
Brent
-Original Message-
From: Adam Fortuno KOVICK [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 2:13 PM
To: [EMAIL PROTECTED]
Cc: MySQL List
Subject: Re: RE: Newbie question...memo field
Brent,
Maybe b
is db?
Thanks for the help.
Brent
-Original Message-
From: Adam Fortuno KOVICK [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 2:13 PM
To: [EMAIL PROTECTED]
Cc: MySQL List
Subject: Re: RE: Newbie question...memo field
Brent,
Maybe but give us more information. I know you moving
> updates?
> Thanks,
>
> Brent
> -Original Message-
> From: Adam Fortuno KOVICK [EMAIL PROTECTED]
> Sent: Friday, August 01, 2003 11:31 AM
> To: [EMAIL PROTECTED]
> Cc: MySQL List
> Subject: Re: Newbie question...memo field
>
>
> Normally I'd say do a s
KOVICK [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 11:31 AM
To: [EMAIL PROTECTED]
Cc: MySQL List
Subject: Re: Newbie question...memo field
Normally I'd say do a select...into...from, but I don't think MySQL
supports that. In lew of that, try this:
(1) Create the new table.
CR
Normally I'd say do a select...into...from, but I don't think MySQL
supports that. In lew of that, try this:
(1) Create the new table.
CREATE TABLE tbl_table_b (
record SMALLINT NULL,
id SMALLINT NULL,
color VARCHAR(10)
);
(2) Insert the values from the source table to the destination.
INSE
