At 11:53 -0800 11/9/04, Fredrick Bartlett wrote:
Why not "TRUNCATE" table...
If you want an empty table, yes. The goal below appears to be
to retain the records after changing one of the columns after an
empty string.
- Original Message -
From: "Paul DuBois" <[EMAIL PROTECTED]>
> At 13:0
Why not "TRUNCATE" table...
- Original Message -
From: "Paul DuBois" <[EMAIL PROTECTED]>
To: "gerald_clark" <[EMAIL PROTECTED]>; "Craig Cummings"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, November 09, 2004
That did the trick. Thanks for the advice.
-Craig
On Tue, 9 Nov 2004, Paul DuBois wrote:
> At 13:06 -0600 11/9/04, gerald_clark wrote:
> >Craig Cummings wrote:
> >
> >>Hi there,
> >>
> >>I have a table with three columns, two varchar(12) identifiers and a
> >>longtext column with very long (som
At 13:06 -0600 11/9/04, gerald_clark wrote:
Craig Cummings wrote:
Hi there,
I have a table with three columns, two varchar(12) identifiers and a
longtext column with very long (some > 50 MB) strings. The size of the
chromosomes.MYD table was about 2.8 GB. The table was used transiently
and I no l
Craig Cummings wrote:
Hi there,
I have a table with three columns, two varchar(12) identifiers and a
longtext column with very long (some > 50 MB) strings. The size of the
chromosomes.MYD table was about 2.8 GB. The table was used transiently
and I no longer needed to store the strings, so in th
