From: Date: July 3 2009 6:54pm
Subject: Re: GSoC Week 8 - June 23-29 | per query variable settings
List-Archive: http://lists.mysql.com/internals/37082
Message-Id: <C673AFF9.A8D%jlukas79@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Sorry wrong data was in the title.  I have got launchpad working finally go=
t
it to recognize my public key. I think my launchpad project link is
bazaar.launchpad.net/~jlukas79/+junk/mysql-server.  I think I understand th=
e
Lex.  It is a linked list right? With a forward and backward set of pointer=
s
to traverse the chain.  I have been trying to look at the Lex setup code.  =
I
noticed that SET X =3D 10; the command send the Lex to make List(). I was
wondering if this would be better to send to my function or take use the Le=
x
structure as is.=20

As implementation I figured since the Lex is essentially a linked list I
would traverse the Lex until the Select statements are reached and break th=
e
linked list. I would then make a List(Set Linked List) and call the set
functions like it is doen normally.  I would then find the Select functions
and send to them. I figure during while traversing the Set statement I coul=
d
copy the chain of variables that are to be Set this way before I send to th=
e
SET function I could retrieve the variables for GET to reset the values
after I perform the SELECT. Does this sound logical or am I off in how the
Lex is setup?


On 7/3/09 11:02 AM, "Sergei Golubchik" <serg@stripped> wrote:

> Hi, Joseph!
>=20
> Sorry for the late reply, I've just returned back home yesterday :(
>=20
> On Jun 28, Joseph Lukas wrote:
>>=20
>> KEY ACCOMPLISHMENTS LAST WEEK
>> Began looking into the full structure of the Lex and deciding how to pas=
s
>> the information my function. Not too much in this explained later.
>=20
> Do you want me to explain that part ? What exactly is unclear ?
>=20
> By the way, you tree is still not on launchpad, right ?
> Can you send me a patch then ?
> This or early next week, please - so that I could look at it before mid
> term evaluation deadline.
> =20
>> KEY TASKS THAT STALLED LAST WEEK
>> Going through the Lex I managed to screw up some code somehow I have
>> yet to figure out and had to use bazaar to revert the code.  Nothing
>> really lost though.
>=20
> good :)
>=20
>> On my proposed schedule: Still on schedule
>> Currently at | Develop initial system base :: Est. May 24 - June 30
>> Skeleton Code in place - Done
>> MySQL recognizes empty function command - done already
>> executes minmal test block such as creates output test file - done
>> command set as reserved word - done
>> functions in SQL command - Done
>> verify data sent, and data structure - In-Progress
>=20
> Great! Just don't forget to send the patch.
> =20
> Regards / Mit vielen Gr=FC=DFen,
> Sergei