List:Internals« Previous MessageNext Message »
From:Sergei Golubchik Date:January 20 2010 6:14pm
Subject:Re: query cache extension
View as plain text  
Hi, Amila!

On Jan 20, Amila Liyanaarachchi wrote:
> Hi Sergei,
> First I tried to parse the incoming query before comparing with the
> QC, my intention was to keep the select list (with table aliases) and
> the column list in the where clause again with the table aliases. For
> simplicity I didn't handle the rest of the things possible to come is
> a query.  But I couldn't finish the implementation due to the tightly
> couple and complex nature of the QC implementation.
> Could you please give me few tips to go try it similar to what
> libmysqlclient does (as you suggested in your previous email).

Walk the execution of, say, mysql_use_result() API call, you will see
how to turn network packets into fields and their data.

But there is a misunderstanding. I did not *suggest* to do that. I only
noted that it could be done, technically, that way. But not everything
that could be done should be done. Working on network packet level,
although possible, is too complex and architecturally wrong. I
personally would never even consider implementing such a solution.
query cache extensionAmila Liyanaarachchi11 Nov
  • Re: query cache extensionSergei Golubchik12 Nov
    • Re: query cache extensionAmila Liyanaarachchi13 Nov
      • Re: query cache extensionSergei Golubchik13 Nov
        • Re: query cache extensionAmila Liyanaarachchi11 Dec
          • Re: query cache extensionRick James16 Jan
Re: query cache extensionAmila Liyanaarachchi20 Jan
  • Re: query cache extensionSergei Golubchik20 Jan