Hi,
>Is it possible to place MySQL data directories on a Linux ramdisk mount?
Oh yes. No fragmentation aftertaste.
Regards,
Gabriel
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
Hi,
> No, not with mine :)
Well , you have the wrong data. Let me post the whole thing to let
people what I'm talking about.
mysql> select * from tt;
+--+--+
| f1 | f2 |
+--+--+
|1 |1 |
|1 |2 |
|2 |3 |
|1 |4 |
+--+-
Hi,
I'm not sure what list this should go to, so I'm sending it to the general
list. It's not about sql or queries it's more of a webmaster problem.
Apologies to the offended.
After sending several messages to the list I started receiving strange
messages. It may be spam, it may be just a viru
> > >Description:
> > HAVING in SELECT is evaluated before WHERE. This is not the
> > correct behaviour as HAVING should deal with the remainder of the WHERE
> > selection (according to manual)
>
> I cannot understand how the following can show that "HAVING in SELECT is
> evaluated before WH
> That is the case. Without a GROUP BY, max() is supposed to apply to the > entire
> table.
Not true. Use of MAX in WHERE clause will show that MAX is applied to
filtered data set. To use my example data set:
mysql> select f2 from tt where f1=2;
+--+
| f2 |
+--+
|3 |
+--+
1 ro
Hi,
I had some private e-mail suggesting that MAX functions should apply to
the full table - as it is the maximum value of the field- and this is why
HAVING clause behaved in that manner.
I'm sure this is not the case since MAX does obey (as it should)
WHERE clause in the query.
To
Hi,
> Your whole query is malformed. You have an aggregate function in the
> having.
It's absolutely legal query. In fact I don't get any error messages that say
otherwise. I'm not SQL guru but I haven't heard that agregate functions have
to be excuded from HAVING clause. To qu
Hi,
this is NOT correct behavior. Where clause returns (1,1) and (1,2). The HAVING
clause should be applied to what WHERE has selected and choose the (1,2)
record.
A quote from the manual "It (HAVING) is applied last, just before items are
sent to the client, with no optimisation