From: | Peter T Mount <peter(at)retep(dot)org(dot)uk> |
---|---|
To: | selvam(at)gelife(dot)com(dot)my |
Cc: | Peter T Mount <peter(at)retep(dot)org(dot)uk>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: pg703: support for Large objects via JDBC PreparedStatement.setBi naryStream() |
Date: | 2001-03-21 14:26:56 |
Message-ID: | 985184816.3ab8ba307673a@webmail.retep.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Quoting selvam(at)gelife(dot)com(dot)my:
>
> I do not understand when people say that pg7.03 is out and some are
> talking
> about 7.1. What is the difference anyway? As far as I know 7.03 is the
> latest. What about 7.1? I am new to postgreSQL. Can someone please
> clarify me?
The latest released version is 7.0.3. However, 7.1 is on it's way (Release
Candidate 1 aka RC1 should have been released last night).
> And added to that, if 7.03 is out, does the jdbc support calling
> stored procedures? cause when I used Calllable Statments in 7.02, there was an
> exception that it was not supported. Please clarify me.
CallableStatement is still not supported. A group of students are working on
it. However the behaviour of throwing an exception is correct.
A workaround is to use PreparedStatement (as in postgres prodecures are
implemented as functions) and use select.
Peter
>
> Regards,
>
> Selvam
>
>
>
>
>
>
> Peter T Mount
>
> <peter(at)retep(dot)org(dot)uk> To: Julian
> Richardson
> Sent by:
> <JRichardson(at)softwright(dot)co(dot)uk>
> pgsql-jdbc-owner(at)post cc:
> "'pgsql-jdbc(at)postgresql(dot)org'"
> gresql.org
> <pgsql-jdbc(at)postgresql(dot)org>
> Subject: Re: [JDBC]
> pg703: support for Large
> objects via JDBC
> PreparedStatement.setBi
> 20/03/2001 11:10 PM naryStream()
>
>
>
>
>
>
>
>
>
> Quoting Julian Richardson <JRichardson(at)softwright(dot)co(dot)uk>:
>
> > I didn't study the code in detail but it looked like there's stuff
> > missing
> > in the Large Objects API too, so it may not even be possible to use
> that
> > as
> > an alternative (I'd rather not anyway, but may have been able to make
> > the
> > setBinaryStream method call into it behind the scenes to do the work)
> >
> > Is there a workaround for this (or preferably a fix for the drivers!!)
> -
> > or
> > does it work in pg6.5 as downgrading may be an option?
>
> No, proper stream support was only introduced in 7.1 :-)
>
> > ps. posted a variation on this to the pgsql-bugs list the other day
> but
> > don't know if it got through - hopefully this one will.
>
> I've been ofline for a couple of weeks so I've got a few K of emails to
> catch
> up with :-(
>
> Peter
>
> --
> Peter Mount peter(at)retep(dot)org(dot)uk
> PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
> RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
>
>
>
>
--
Peter Mount peter(at)retep(dot)org(dot)uk
PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-03-21 19:33:25 | patches for jdbc1 (fwd) |
Previous Message | Juhan-Peep Ernits | 2001-03-21 09:29:23 | Re: Re: [INTERFACES] Trouble with JDBC2 ResultSet.getDate() |