Thanks for your reply.This works for me.
Can you tell me why the number is 9?
when I try others,it can not work at all.
On Wed, Apr 30, 2008 at 8:08 PM, Baron Schwartz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Try forming the comments like this:
>
> /*!9
> * comment text here
> */
>
> See if
Thanks for your reply.
I know this way to comment outside of a store procedure,But this is not my
need.
On Wed, Apr 30, 2008 at 10:49 PM, Saravanan <[EMAIL PROTECTED]> wrote:
>
> Use
>
> alter procedure procedure_name comment 'comments string'
>
> Saravanan
>
>
> --- On Wed, 4/30/08, Moon's Fathe
On Sat, May 3, 2008 at 6:00 PM, Patrick Aljord <[EMAIL PROTECTED]> wrote:
> SELECT count(*) as counted,
> u.login
> FROM posts c
> left join users u on posts.poster_id=u.id
> group by c.user_id
> having counted>1
> order by counted DESC
> LIMIT 20
This is a bad query. You are abus
hey all,
I have my query that counts posts per user:
SELECT count(*) as counted, c.user_id FROM posts c group by c.user_id
having counted>1 order by counted DESC LIMIT 20
I wanted to add user login for each count so I did:
SELECT count(*) as counted, u.login FROM posts c left join users u on
p
On 29-Apr-08, at 10:41 AM, Andrew Braithwaite wrote:
Hi,
Three things...
1. You need to let us know what the DB server will be doing. Many CPU
cores are only important of you have many CPU intensive MySQL
connections in parallel. Will you have a read-intensive or
write-intensive database lo
On 28-Apr-08, at 11:26 AM, Francisco Rodrigo Cortinas Maseda wrote:
The other counterpart is that if you can put the entire databases on
RAM, your disk needs are not so high. So if you can afford that.
Silly question, but with MySQL default configuration (say, huge.cnf),
does it automat
