[Mulgara-dev] Fixing transactions.&In-Reply-To=F9B19727-3481-4131-A870-80FC3BA4D784@netymon.com

[Paul Gearon]

Hi David,

On 10/4/06, David Moll <DMoll at viewpointusa.com> wrote:
> I am very interested in helping, but I have only just started looking at
> Mulgara. I am making some progress, having managed to build Mulgara in
> Eclipse and get the EmbeddedMulgaraServer running.

Not bad.  It took me a while too.  Mulgara really is built around the
command line and Ant, so it had to be shoehorned into Eclipse.  I
always build with ant, and 99 times out of 100 I run from the command
line and edit with vi.

> However, getting a good
> understanding of the overall layout of the project is proving to be
> difficult. Is there a good starting point that I can use to jump off and go
> along merrily learning about the structure and workings of the project?
> I'm not looking for any hand-holding, just a place to begin reading. I'd
> rather not flood the dev list with lots of FAQ-style questions.

Actually, messages on the list may be useful, since the architecture
is not properly documented anywhere.

In the meantime, try looking at the code from ItqlInterpreter down to
DatabaseSession.  ItqlInterpreter does the iTQL parsing in order to
create a Query object.  Follow this across the Session interface and
try to follow how an Answer gets resolved.  It goes through joins and
all sorts of things.

While doing all of this you'll see a factory create a Resolver object,
and the resolve() method will be called on it.  Don't go beyond this
point, as it is a COMPLETELY different conceptual layer.  Not saying
you should never look at it, but it's a good boundary while trying to
follow what's going on.

Let me know if anything here is confusing.

Paul