Skip site navigation (1) Skip section navigation (2)

Re: Problem with Utilizing executeBatch() with stored procedures

From: "Kranti Parisa" <kranti(dot)parisa(at)gmail(dot)com>
To: "Dave Cramer" <pg(at)fastcrypt(dot)com>
Cc: "Kris Jurka" <books(at)ejurka(dot)com>, pgsql-jdbc(at)postgresql(dot)org, guyr-ml1(at)burntmail(dot)com
Subject: Re: Problem with Utilizing executeBatch() with stored procedures
Date: 2007-05-07 13:29:23
Message-ID: 4478b4ac0705070629o7fa9b9ddw581544bda17f1a32@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
ook..

I havent done this before.. i will try to get that. but if its possible for
you, please send me the jar file. it would be a great help.

On 5/7/07, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
> Sure, just grab the source from CVS and build the jar.
> Dave
> On 7-May-07, at 9:19 AM, Kranti Parisa wrote:
>
> Hi,
>
> So finally.. we cant solve this problem now?
>
>
>
> On 5/7/07, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
> >
> > Crap, you're correct,
> >
> > I just committed it.
> >
> > Dave
> > On 7-May-07, at 9:02 AM, Kris Jurka wrote:
> >
> > >
> > >
> > > On Mon, 7 May 2007, Dave Cramer wrote:
> > >
> > >> It's been fixed in the lastest version.
> > >>
> > >
> > > When was this fixed?  As far as I recall you made a patch to fix
> > > this, but never committed it or shared it with the list.  If you
> > > believe you committed this, could you point us to the commit message?
> > >
> > > Kris Jurka
> >
> >
>
>
> --
> ------------------
> Best Regards
> Kranti Kiran Kumar Parisa
> Mobile: +91 - 9849 - 625 - 625             +91 - 9391 - 438 - 738
>
>
>


-- 
------------------
Best Regards
Kranti Kiran Kumar Parisa
Mobile: +91 - 9849 - 625 - 625             +91 - 9391 - 438 - 738

In response to

Responses

pgsql-jdbc by date

Next:From: Dave CramerDate: 2007-05-07 13:47:00
Subject: Re: Problem with Utilizing executeBatch() with stored procedures
Previous:From: Dave CramerDate: 2007-05-07 13:26:56
Subject: Re: Problem with Utilizing executeBatch() with stored procedures

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group