Andrei Elkin wrote:
> >> >> >> As a comment on it, I thought the test would lists all
> kinds of query
> >> >> >> on a temporary table and to print the content of the
> binlog in the
> >> >> >> end.
> >> >> >
> >> >> > I agree to check all update querys that using temporary table
> would make
> >> >> > the test complete, but I think the idea to print the content
> of the
> >> >> > binlog is not good, because that would make the test dependent
> on the
> >> >> > format of the binlog dump format, which might change from time
> to time.
> >> >>
> >> >> Well, not all the binlog but only
> >> >>
> >> >> $MYSQL_BINLOG binlog | grep 'pseudo_thread_id'
> >> >>
> >> >> would be relevant to show in the results.
> >> >>
> >> >
> >> > but the thread_id number might change.
> >> >
> >>
> >> well, then mask out the number. What we really need is the line with
> >> set @@session.pseudo_thread_id.
> >>
> >
> > Hmm, then we cannot check if the number is correct, i.e. the numbers for
> > different connections are differenct, and for the same connection they
> > are the same.
>
> Initially, my aim was less ambitious, merely to show presense
> `set @@session.pseudo_thread_id' per a query.
> As to checking uniqueness of the pseudo_thread_id, which is a good point,
> there can be some ways:
> if there is no sort, uniq shelltools then,
> to store grep results into file and LOAD DATA it into a (temp:-)
> table with the number at `the pseudo_thread_id=' to correspond to a
> unique attribute of the table, and see if `LOAD DATA' fails.
>
Thanks for clarifying, I think it can work, but probably a little bit
overkilling :-)
>
>
