Do you know - would that be of any help?
23.2 The Query Log
If you want to know what happens within mysqld, you should start
it with --log[=file]. This will log all connections and queries
to the log file (by default named `'hostname'.log'). This log can
be very useful when you suspect an error
WS>> Oh, I see, you would like to connect this information with the
WS>> pid, right? I wouldn't know how to do that. How do you get a pid?
WS>> Is this something MySQL could provide?
> No, not with the pid.
> With the number of places from where sql queries are executed and
> the numb
BAUMEISTER Alexandre wrote:
>
> Bonjour Justin,
>
> JF> I don't know why I got interested in this thread...
>
> More important (or less), why are you so negative ?
>
Je ne suis pas contre. I just haven't felt the need for
this, but after reading your scenario, I can't understand
why. Email
Bonjour Scott,
SH> Beyond that, you can already accomplish 90% of what you'd want by
SH> simply coding your queries as "/* Comment */ SELECT ...", and so
SH> on. For connections which are not currently running a query, this
SH> won't work - but in my experience, you usually don't care muc
Bonjour Justin,
JF> I don't know why I got interested in this thread...
More important (or less), why are you so negative ?
JF> I suppose you don't need a change to the wire protocol if
JF> you have, logically, something like below. The API has
JF> to be changed, however.
JF> id = do_a
Bonjour Justin,
"user agent" was just an example of what the commentary could be.
You could put what you want as long as it's a string.
I agree with you and I already had this reflection that it could be
a modification that could create some problems to some.
Instead of modifyin
l Message-
From: Alexandre BAUMEISTER
To: [EMAIL PROTECTED]
Sent: 7/4/2001 2:59 PM
Subject: Re: Proposition: Attach a comment to each connection
Bonjour,
I sent this post a few days ago but it didn't get a lot of
contributions.
Wouldn't it be an interresting feature ?
> > > Wh
I don't know why I got interested in this thread...
I suppose you don't need a change to the wire protocol if
you have, logically, something like below. The API has
to be changed, however.
id = do_a_connedtion(arg)
set_comment_on_connection(id, "this_is_my_comment")
// later
some_array = g
This thread has been "interesting" to follow. But I considered it
completely "blue sky".
Are you guys supporting a change to the MySQL wire protocol? Are
you guys supporting a change to _all_ API's that currently use
MySQL that would then have to stick somewhere all these "nice"
things in the e
>> The only thing I would like is to be able to attach a comment to a
>> connection id which could be returned by the "mysqladmin process"
>> command. And something that would not add more load to Mysql nor
>> more coding in the client.
AB> Yes!! Great idea. This would be helpfu
> The only thing I would like is to be able to attach a comment to a
> connection id which could be returned by the "mysqladmin process"
> command. And something that would not add more load to Mysql nor
> more coding in the client.
Yes!! Great idea. This would be helpful for ho
Bonjour Werner,
>> Am I naive or is this a viable proposition?
WS> Oh, I see, you would like to connect this information with the
WS> pid, right? I wouldn't know how to do that. How do you get a pid?
WS> Is this something MySQL could provide?
No, not with the pid.
With the number of pla
Bonjour Werner,
My web site as a lot of hits (really!), it's load balanced on the
web side on more than 30 servers.
I've to save database load as much as possible.
The problem with your implementation is that it needs at least one
more insert query for each page or even more if
> Am I naive or is this a viable proposition?
Oh, I see, you would like to connect this information with the
pid, right? I wouldn't know how to do that. How do you get a pid?
Is this something MySQL could provide?
--
Herzlich
Werner Stuerenburg
How about tracking your own record until then? Create a table and
insert a record for each connection.
If you would use a class to connect like db_mysql.inc from
PHPLIB, it would be a snap to implement. From php, you know all
sorts of variables to identify your general setting.
I assume that the
Bonjour,
I sent this post a few days ago but it didn't get a lot of contributions.
Wouldn't it be an interresting feature ?
> > > When you have a big web site with a lot of pages, programs,
> > > cronjobs, applications ... connecting to Mysql, it's sometimes
> > > difficult
.
D'Arcy
- Original Message -
From: "Siomara Pantarotto" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 02, 2001 1:52 PM
Subject: Re: Proposition: Attach a comment to each connection
> descriptive usernames??
TECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: Re: Proposition: Attach a comment to each connection
>Date: Mon, 2 Jul 2001 13:42:42 -0400
>
>I do this by using a whole bunch of descriptive usernames. It is more work
>than your idea, but you could use this method for n
]>
Sent: Monday, July 02, 2001 11:38 AM
Subject: Proposition: Attach a comment to each connection
> Bonjour,
>
> When you have a big web site with a lot of pages, programs,
> cronjobs, applications ... connecting to Mysql, it's sometimes
> difficult
Bonjour,
When you have a big web site with a lot of pages, programs,
cronjobs, applications ... connecting to Mysql, it's sometimes
difficult to find from where a given query/connection comes from.
And it's sometimes urgent to find the origin of a disturbing query.
So
20 matches
Mail list logo
