I agree, 100%. We live in a mixed environment of UNIX and Windows and as
such, we've assumed case insensitivity in our apps. I know that this is bad
practice, but forcing this flag on us is and even worse practice. This
should always, always be an option.
I wont be able to upgrade until this is
Kim,
I use WRITE locks extensively with MySQL 4 with a large distributed
application.
Your example logs indicate that your test application obtained a READ lock,
which will not block other select requests from accessing the table. Only a
WRITE lock will cause subsequent select requests to be
Lemasson,
When you refer to a column as a primary key, I tend to think that this key
will be your main relationship point to the data in your table. Now, when
you combine the primary key concept with a BLOB (binary large object), it
seems to me that you are almost defeating the purpose of a
Roger,
Thanks for the info!
I am examining the file in a HEX editor right now and have identified the
pattern. The table size divided by the pattern byte length is 8 bytes. The
last byte is always one of three characters ('S', 'B', or 'U') as defined by
the program that feeds this table. So I
Egor,
Thanks for the info. However, like I said, I already have local-infile=1
and set-variable = local-infile=1 in my my.ini on the server. I also have
already done 'show variable like '%infile%' ' and receive local_infile
ON in the result set.
I run the command line client with
Versions:
Server is Win32 MySQL max 4.0.16
Client is FreeBSD MySQL 4.0.13
-- R
Should work.
What are the server and client versions?
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
Typically, this is the kind of query I see at MS-SQL houses. :)
-- R. Deuce
- Original Message -
From: Matt W [EMAIL PROTECTED]
To: Thai Thanh Ha [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, November 18, 2003 5:28 PM
Subject: Re: Please help DB Error: unknown error
Hi Thai,
Running Win2K and the latest MySQL 4 release. I have a little more than half
a billion rows in three databases and about 50 tables. For about six hours a
day, MySQL is hammered like there's no tomorrow adding/deleting/updating
millions of rows. No problems at all.
I've been using MySQL for almost
Casey,
I would consider, on the most basic level, a method like this:
Contacts (all the company contact info, etc) using primary key contact_id -
IndustrialRelationships table
- industry_id primary key on Industries table (all the different type of
industries)
So, in the IndustrialRelationships
