Hi Jim,
Thanks for the quick reply.
Is it safe to assume each of the source code top level directories as
modules? E.g client,sql e.t.c. This would then imply that there are
around roughly 36 modules in mysql?? (I am analyzing mysql-4.1.10
source code for now)
If someone were to layer them would the following layering make sense??
Layer 3 (Application): client, tests
Layer 2 (QueryProcessing): sql
Layer 1 (StorageManagement): heap, innobase, myisam, ndb, isam,
bdatabase, myisammrg, merge
Layer 0 (library/utility) : mysys,libmysql,libmysqld,libmysql_r,
cmd-line-utils, extra, mysqltest, netware, os2, pstack,
regex, zlib, vio, strings, SSL, support-files, tools, include,
dbug
There are too many modules in level 0 as I did not know where to place
some of them, especially libmysqld. I could not understand from the
documentation what exactly is the purpose of libmysqld.
Will someone please comment.
Thanks a lot.
Regards
Girish
> -----Original Message-----
> From: Jim Winstead [mailto:jimw@stripped]
> Sent: Saturday, June 03, 2006 1:28 AM
> To: Girish Maskeri Rama
> Cc: internals@stripped
> Subject: Re: mysql architecture
>
> On Fri, Jun 02, 2006 at 04:59:20PM +0530, Girish Maskeri Rama wrote:
> > We were trying to derive and analyze mysql architecture
> > layering and were surprised to find some files like sql_string.cc
and
> > sql_string.h in the 'client' directory.
>
> Yes, these really shouldn't be there. We're working on refactoring
some
> of the internal libraries, including the string types and classes, so
> these will be removed eventually.
>
> > Will someone please let us know what was the reason for grouping
these
> > files in the 'client' directory. Also is there any document
discussing
> > mysql architecture and how the modules are layered?
>
> There is some information about this in the Internals documentation at
> http://dev.mysql.com/doc/internals/en/index.html
>
> It may be a little bit out of date. (It hasn't been updated to reflect
> some of the reorganization in 5.1, at least.)
>
> If you have more questions about the internals, don't hesitate to ask
on
> internals@stripped.
>
> Jim Winstead
> MySQL Inc.
**************** 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***
