On Wed, Jun 21, 2006 at 05:33:30PM +0530, Girish Maskeri Rama wrote:
> [>>>] Does this mean that client is at a layer above libmysql ,
> libmysql_r and libmysqld?
yes.
> > > 1. There are 3 versions of sql_string.h : client/sql_string.h,
> > > libmysqld/sql_string.h and sql/sql_string.h. Do we need 3 versions?
> >
> > likely just symlinks.
>
> [>>>] Iam analysing the sourc-code of mysql-4.1.12. The files
> sql/sql_string.h and client/sql_string.h are actually different. Are
> they just symlinks in the latest version?
they are out-of-date copies. there is a redundancy here that we just
have not had time to clean up, because the layering is not correct.
> > > 3. There are function calls from sql (in layer 2) to libmysqld (in
> > > layer 3) . For example function "query_cache_end_of_result" in file
> > > sql/sql_cache.cc calls the function "emb_count_querycache_size" in
> file
> > > libmysqld/emb_qcache.cc. Is this intended?
> >
> > probably in #ifdef
>
>
> [>>>] Yes. It is in #ifdef. So it is okay for sql to call libmysqld?
> That should not be considered as a call to layer above?
sql is not "calling" libmysqld. libmysqld is essentially a parallel to
sql. sql is the normal server, libmysqld is the embedded server. there
are files that are shared between the two directories, but live
primarily in the sql directory.
> Do you know if there has been a major structural change in any of the
> versions? Also SQL directory seems to be too big are there any plans to
> split it up?
there has been some refactoring in 5.1, but that is mostly related to
reorganizing the storage engines. i'm not aware of any plans to split up
the sql directory in any significant way.
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the
> use of the addressee(s). If you are not the intended recipient, please notify the sender
> by e-mail and delete the original message. Further, you are not to copy, disclose, or
> distribute this e-mail or its contents to any other person and any such actions are
> unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution
> to minimize this risk, but is not liable for any damage you may sustain as a result of any
> virus in this e-mail. You should carry out your own virus checks before opening the e-mail
> or attachment. Infosys reserves the right to monitor and review the content of all
> messages sent to or from this e-mail address. Messages sent to or from this e-mail address
> may be stored on the Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***
please turn off this nonsense when sending emails to a public mailing
list. thanks.
jim
