Hi Sergei,
Sorry for the inconvenience , now you can comment on the document :)
On Tue, Mar 22, 2016 at 1:25 PM, Sergei Golubchik wrote:
> Hi, Varun!
>
> On Mar 22, Varun Gupta wrote:
> > Hi Sergei ,
> > I have created a draft proposal and submitted to summerofcode website.
> > I haven't written
Hi, Varun!
On Mar 22, Varun Gupta wrote:
> Hi Sergei ,
> I have created a draft proposal and submitted to summerofcode website.
> I haven't written the project timeline yet. Please I would appreciate
> if you could go through it and leave comments so that I can make any
> necessary corrections.
I
Hi Sergei ,
I have created a draft proposal and submitted to summerofcode website. I
haven't written the project timeline yet. Please I would appreciate if you
could go through it and leave comments so that I can make any necessary
corrections.
On Mon, Mar 21, 2016 at 2:34 PM, Sergei Golubchik w
Hi, Varun!
On Mar 21, Varun Gupta wrote:
> Hi Sergei,
>
> 4) :create an Item_sum_sp to be able to use aggregate stored functions in
>queries.
> Does this mean we can have the aggregate stored functions in the SELECT ,
> WHERE etc clauses?can you give me more details about this.
Yes, of cours
Hi, Varun!
On Mar 19, Varun Gupta wrote:
> Hi Sergei,
> I have gone through the code you suggested. I have got a good understanding
> of what the code actually does. So now I wanted to start writing the
> proposal for the idea. Can you tell me what all is needed to written in the
> proposal. I am
Hi Sergei,
I have gone through the code you suggested. I have got a good understanding
of what the code actually does. So now I wanted to start writing the
proposal for the idea. Can you tell me what all is needed to written in the
proposal. I am asking for a template or something that could guide
Hi Sergei,
Thanks that answers my question, I will soon get back with questions .
On Sun, Mar 6, 2016 at 2:52 PM, Sergei Golubchik wrote:
> Hi, Varun!
>
> On Mar 06, Varun Gupta wrote:
> > Hi Sergei,
> > I understand that having a cursor like syntax we would have to write
> some
> > new code .
Hi, Varun!
On Mar 06, Varun Gupta wrote:
> Hi Sergei,
> I understand that having a cursor like syntax we would have to write some
> new code . What I would have liked to know is that the more details should
> be discussed which need to be incorporated in the implementation of the
> aggregate func
Hi Sergei,
I understand that having a cursor like syntax we would have to write some
new code . What I would have liked to know is that the more details should
be discussed which need to be incorporated in the implementation of the
aggregate functions. Basically what I am asking is what all detai
Hi, Varun!
On Mar 04, Varun Gupta wrote:
> With the syntax more or less clear to us, can we have a discussion about
> how we have to go on with the implementation for the aggregate functions.
> Firstly I thought I should look at the implementation of CREATE FUNCTION,
> any other suggestions ?
Sur
With the syntax more or less clear to us , can we have a discussion about
how we have to go on with the implementation for the aggregate functions.
Firstly I thought I should look at the implementation of CREATE FUNCTION,
any other suggestions ?
On Thu, Mar 3, 2016 at 4:56 PM, Varun Gupta
wrote:
With the cursor approach, I think it looks more easier to understand . Also
it covers the point that the state has to be saved when the function is
called for different values of x ,so we know the approach is correct. We
are using the function attribute X in calculating the sum. I don't
understand
Hi, Varun!
On Mar 02, Varun Gupta wrote:
> Well in HSQL we have the limitation of having maximum of 4 arguments , but
> in our syntax we can increase the number of arguments.The main thing is
> what I understood from HSQL and PostgreSQL is that an aggregate function
> would have 2 states.
> 1) wh
Well in HSQL we have the limitation of having maximum of 4 arguments , but
in our syntax we can increase the number of arguments.The main thing is
what I understood from HSQL and PostgreSQL is that an aggregate function
would have 2 states.
1) when we compute the result that is the result keeps on
Hi, Varun!
On Mar 02, Varun Gupta wrote:
> Well i have checked out the syntax for the databases for aggregate
> functions. I thought using the syntax similar to that of HSQL would be
> good. In it if we are having N tuples then we are computing the values for
> the N rows and then after that we ma
Well i have checked out the syntax for the databases for aggregate
functions. I thought using the syntax similar to that of HSQL would be
good. In it if we are having N tuples then we are computing the values for
the N rows and then after that we make another call and return the value
for the funct
16 matches
Mail list logo
