Michael Dykman wrote on Fri, Sep 21, 2007 at 01:37:57PM -0400:
> There is a setting in your my.cnf which specifies the threshold at
> which temporary tables will be put to disk instead of being held in
> RAM. This has to be a dynamic decision as the system has to consider
> available RAM and the s
As others have mentioned, mysql doesn't handle IN queries efficiently.
You can try changing it to using derived tables/subqueries. I did some
quick tests and the explain shows a different analysis.
select comment, gid, date_posted from tbl
JOIN
(select max(id) as mid
from tbl where gid in ( 1234,2
There is a setting in your my.cnf which specifies the threshold at
which temporary tables will be put to disk instead of being held in
RAM. This has to be a dynamic decision as the system has to consider
available RAM and the size of any given temporary table.. under
normal circumstances, the my.
Erik,
Even is you eliminate the subquery (which I have used efficiently in
the past, but they are always something to be careful of), the IN
clause is going to kill you.. above a certain number of elements in
that clause, the optimizer will go straight to full table scan. This
drawback is well-k
Erik, I think the main reason your query is running slowly is the use of a
subselect. MySQL does not generally perform well with subselects, though
work continues in that area.
There is also a problem/situation in MySQL in that you can't use MAX/GROUP
BY functions quite the way you can in other d
Hello everyone,
The app server in this case is PHP, and the database is MySQL 5.0.22
on RedHat linux
I've got a database with about 7.5K records in it that I expect to
start growing very quickly ~10-12K records per day. The storage
engine is InnoDB. This table is growing quickly and will
Baron Schwartz wrote on Thu, Sep 20, 2007 at 07:46:44PM -0400:
> Michael explained it well, but just to say it a different way, the
> temporary table is created as an intermediate step in the table, and is
> implicit, not explicit. So it's not "sent" to the slave -- the query is
> sent to the s
Hi Krishna,
Have you set this parameter
innodb_data_file_path=
On 9/21/07, Krishna Chandra Prajapati <[EMAIL PROTECTED]> wrote:
>
> Hi All,
>
> I am working my.cnf file. I would like to know that whether any component
> of
> my.cnf has to be setup before setting up the data on mysql.
>
> I am n
Hi All,
I am working my.cnf file. I would like to know that whether any component of
my.cnf has to be setup before setting up the data on mysql.
I am not able to change innodb_log_file_size.
Please help me.
Hi Edward. Thank you very much for your answer.
I tried adding these two lines after DB connection (PHP code):
---
mysql_query ("SET NAMES utf8;");
mysql_query ("SET CHARACTER_SET utf8;");
--
but it won't work :(
The solution you provided could be right because it works, but I don't
dare
> Hi.
>
> Using mySQL 4.1.22, I'd like to carry out an SQL query to find a
> string containing acute vowels.
>
> mytable:
> - item1:
> --- firstname: Antonio
> --- lastname: Fernández
> --- comments: he's from Spain
>
> My SQL query:
> --
> SELECT id FROM mytable WHERE MATCH(firstname, lastnam
My ft configuration in /etc/my.conf:
--
ft_min_word_len=1
ft_stopword_file=''
-
On 9/21/07, thomas Armstrong <[EMAIL PROTECTED]> wrote:
> Hi.
>
> Using mySQL 4.1.22, I'd like to carry out an SQL query to find a
> string containing acute vowels.
>
> mytable:
> - item1:
> --- firstname: Anto
Apart from the character-set, did you check your collation-sequences?
SHOW GLOBAL VARIABLES like "collation%";
collation sequences can be set on the server-level, database-level,
table-level...
suomi
thomas Armstrong wrote:
Hi.
Using mySQL 4.1.22, I'd like to carry out an SQL query to find
Finally I decided to use:
--
SELECT id FROM mytable WHERE MATCH(firstname, lastname, comments)
AGAINST ('+"johnie"' IN BOOLEAN MODE) ORDER BY firstname, lastname
It works (except with acute vowel words in UTF8).
Thank you very much.
On 9/20/07, Baron Schwartz <[EMAIL PROTECTED]> wrot
Hi.
Using mySQL 4.1.22, I'd like to carry out an SQL query to find a
string containing acute vowels.
mytable:
- item1:
--- firstname: Antonio
--- lastname: Fernández
--- comments: he's from Spain
My SQL query:
--
SELECT id FROM mytable WHERE MATCH(firstname, lastname, comments)
AGAINST ('+"f
ûµû5ßá:9jÃ`)c¹Ôæº|Õ¨åóûªéS{>]²¥eÑ Ü
qá8'´?²|ïðC°
¹v{°MÀqþò®o÷Qnùc¦2JB§¶5Aw¿{YÕÑízGÔþHìÒb;â©ür¾øï²!,lsRÂ|MNµ4â¦
±0¨?Û¬<:98ñÛMn9°Z5te®HÇô3öÐ;;õaö{Piç7.kÃâÀßÇLÆÈVéÛÛ²(C,z¾sï^wøÝ]snE2L§aüÁgtÚ{ üMñk£[,&9²òF%ÝNU6ºçÜnS0¨K
d4Þ]Ïby¯C;EÜRÞÞttêqûß MÄýøçƯiêÉ|K
16 matches
Mail list logo
