Rezal wrote:
> hello,
> i got a really long text to put in mysql
> n when i use longtext field, it isnt enuff
>
> Can u help me pls ??
>
> thx in advance
> feroze
Sheesh! Over 4 GB in a single row? That doesn't make much sense.
Why not store the text in a file on the filesystem instead?
And jus
Rezal writes:
> hello,
> i got a really long text to put in mysql
> n when i use longtext field, it isnt enuff
>
> Can u help me pls ??
>
> thx in advance
I'll do my best to decipher your message... you have something
that's bigger than the maximum size of a LONGTEXT and you want
to put in in
hello,
i got a really long text to put in mysql
n when i use longtext field, it isnt enuff
Can u help me pls ??
thx in advance
feroze
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://
Hi!
> "macbethh" == macbethh writes:
macbethh> PLATFORM:
macbethh> MySQL Server Version: 3.23.42-max-nt (on SQL Server 2000), 3.23 (on Caldera
Linux) [Latest stable versions]
macbethh> MyODBC Version:2.50.39
macbethh> Client OS Version= Windows 2000 Server
macbethh> Client Program
Cenk,
if the table type is InnoDB, then this is a known bug and it was fixed to
3.23.44. The bug only happens if the table is empty and you do a SELECT
MAX(col) where col is a part, but not the first part of a multi-column
index. Please see the 3.23.44 release note posted today to this same maili
PLATFORM:
MySQL Server Version: 3.23.42-max-nt (on SQL Server 2000), 3.23 (on Caldera Linux)
[Latest stable versions]
MyODBC Version:2.50.39
Client OS Version= Windows 2000 Server
Client Program = ODBCTest 3.00
PROBLEM:
When I run the following commands MYSQL crushes. It says ["The inst
