Hi All,
The temporary table wasn't a better idea,
the problem is that if the search returns 1500+
rows ( on a 20 000 recs table), the population of
temporary table is still slow making no significant difference.
Well, I'm in a strange situation as for the moment.
I've created helper tables, eg to
Hi All, this was already posted on mysql forum preformance,
but forums are really slow, so sorry for the crosspost :)
My objective is to implement quick, really quick complex fulltext search
with 'order by' ( 2 seconds).
The actual table I'd like to search is `lot`. I've created 2 helper
tables
I found your query hard to understand, however it seems the optimizer
could read it just fine. I VERY MUCH dislike using the comma-separated
list of table names to declare INNER JOINS. I think it allows me too much
opportunity to accidentally create a Cartesian product by accidentally
Hi,
Try to add an index on join fields ( search.lot_id,
exchange_rate.currency_id,lot.currency_id)
Your query can not use an index to sort because MySql can use only 1
index to search and sort and your sort is a function so it scans
result rows and then it sorts the working table.
Santino
At
Greetings,
I've got two tables that I want to join on building and room. Right
now I'm doing it on Building Name, but I was wondering if it would be
better to have a column for the building number in each table and do the
join on that instead. Is it better to join on numbers rather than
At 04:58 PM 2/17/03 +0100, you wrote:
Your message cannot be posted because it appears to be either spam or
simply off topic to our filter. To bypass the filter you must include
one of the following words in your message:
sql,query,queries,smallint
If you just reply to this message, and include
sql,query,queries,smallint
I am in the process of designing a form and I am a little confused.
I would like to have a scrolling window, in which the user can
select multiple
items. For example, the scrolling window may contain operating
systems, and the
user has the ability to select multiple
It's really not all that different that source code. For each
application I build, I tend to put the source code in our CVS
repository long with the $foo.sql file(s) to reconstruct the tables.
Just as there's nothing preventing me from deploying a new release of
an application before
the db structure, I have to jot it down in a text file
and later copy-paste it to the production db. Of course, as anything
that is done manually, this can (and already has) lead to problems if
the text file is not kept in sync with the changes in the db.
So what I'm looking for is something like
here) for development and one database for the production
system. Now, whenever I change the db structure, I have to jot it
down in a text file and later copy-paste it to the production db. Of
course, as anything that is done manually, this can (and already
has) lead to problems if the text file
10 matches
Mail list logo
