I submitted an "attempt#2" or "take 2" of a patch to fix the util.Serialize
and jdbc2.PreparedStatement classes so that the serializing of a java class
into the database works more that it did before.
The code to "serialize" a java class instance into a table in the database
has existed in the
Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> Hmm OIDs would be optional in 7.2.
> Is it known(announced) to pgsql-jdbc list ?
Doesn't seem particularly relevant to this issue though. An application
that's using OIDs to identify rows would certainly not choose to create
its tables without OIDs.
Tom Lane wrote:
>
> Ned Wolpert <[EMAIL PROTECTED]> writes:
> > Should the backend support the function getLastInsertedOID() or even
> > getLastInsertedPrimaryKey() (or both)?
>
> I don't think you have any chance of doing the latter --- for one thing,
> how are you going to declare that function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-Aug-2001 Rene Pijlman wrote:
> What should the semantics be exactly?
>
> How about the multiple INSERT's i've been reading about on
> hackers? ... Only the OID of the last row inserted by the
> statement?
>
> How about an UPDATE statement that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23-Aug-2001 Tom Lane wrote:
>> I assume this OID would be associated with a client connection.
>> Is this going to work with client side connection pooling?
>
> Good point. Will this really get around the original poster's problem??
It must. If
Rene Pijlman <[EMAIL PROTECTED]> writes:
> On Thu, 23 Aug 2001 14:44:19 -0400, you wrote:
>> seems doable and reasonable to me: whenever an OID is returned
>> to the client in an INSERT or UPDATE command result, also stash it in
>> a static variable that can be picked up by this function.
> What
On Thu, 23 Aug 2001 14:37:27 -0400, you wrote:
>a patch [...] that fixes the ability to "serialize" a simple java class
>into a postgres table.
>
>The current cvs seems completely broken in this support, so the patch
>puts it into working condition, granted that there are many limitations
>with
> On Thu, 23 Aug 2001 10:46:18 -0400 (EDT), Bruce Momjian wrote:
> >Uh, CHANGELOG? :-)
> >
> >No, I haven't been doing that, figuring I would update it in the main
> >release notes. However, I haven't started doing that yet, and in fact I
> >don't think I know enough about jdbc to know how to de
[join tables in different databases]
>Can you really do this?! that would be great! how is it done? I understand
>accessing multiple databases, but I can't figure out how I would do a JOIN
>across them.
Apparently you are actually awake when you read this list, I
wasn't :-)
OTOH, if the PostgreS
Attached is a patch to fix the current issues with building under jdbc1.
This patch moves the logic that looks up TypeOid, PGTypeName, and
SQLTypeName from Field to Connection. It is moved to connection since
it needs to differ from the jdbc1 to jdbc2 versions and Connection
already has di
On Thu, 23 Aug 2001 14:44:19 -0400, you wrote:
>Ned Wolpert <[EMAIL PROTECTED]> writes:
>> Should the backend support the function getLastInsertedOID()?
>
>seems doable and reasonable to me: whenever an OID is returned
>to the client in an INSERT or UPDATE command result, also stash it in
>a stati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I like your function name, get_last_returned_oid(). That works for me.
On 23-Aug-2001 Tom Lane wrote:
> Ned Wolpert <[EMAIL PROTECTED]> writes:
>> Should the backend support the function getLastInsertedOID() or even
>> getLastInsertedPrimaryKey() (
On Thu, 23 Aug 2001 10:46:18 -0400 (EDT), Bruce Momjian wrote:
>Uh, CHANGELOG? :-)
>
>No, I haven't been doing that, figuring I would update it in the main
>release notes. However, I haven't started doing that yet, and in fact I
>don't think I know enough about jdbc to know how to describe the i
Ned Wolpert <[EMAIL PROTECTED]> writes:
> Should the backend support the function getLastInsertedOID() or even
> getLastInsertedPrimaryKey() (or both)?
I don't think you have any chance of doing the latter --- for one thing,
how are you going to declare that function's return type? But the
forme
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(For those unfamiliar with the topic, looking for a way to get the last
inserted OID through a sql call, rather than a method call off the JDBC
driver)
On 23-Aug-2001 Barry Lind wrote:
> I would only agree to this functionality if it where a backend
Ned,
I would only agree to this functionality if it where a backend function.
By putting it in the front end, you now need to front end to
understand the special function. (And then you we are likely going to
have requests that this special function be available in all the front
ends JDBC
> Bruce,
>
> I can try to fill in whatever I can. Where is it? Can you fill in as
> much as you can?
>
Uh, there is a CHANGELOG file in the top level jdbc directory. We
usually don't list interface-specific changes in the release notes.
Instead we update a CHANGELOG file in the directory for
Bruce,
I can try to fill in whatever I can. Where is it? Can you fill in as
much as you can?
Dave
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
Sent: August 23, 2001 10:46 AM
To: Peter T Mount
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [JDBC] Re: Couple o
> Quoting Bruce Momjian <[EMAIL PROTECTED]>:
>
> > > The other reason for telling people who are experiencing problems
> > with
> > > the driver to get the latest version is that their bug has probably
> > > already been fixed.
> > >
> > > However a certain degree of caution should probably be
* "Marc G. Fournier" <[EMAIL PROTECTED]> wrote:
|
| have a database behind a firewall ... we'd like to make connections
| available to that machine through a machine outside of the firewall, so
| that its a secure connection to the "proxy", and in-secure from
| proxy->database ...
|
| the 'client
Quoting Bruce Momjian <[EMAIL PROTECTED]>:
> > The other reason for telling people who are experiencing problems
> with
> > the driver to get the latest version is that their bug has probably
> > already been fixed.
> >
> > However a certain degree of caution should probably be exercised
> here
Quoting "Marc G. Fournier" <[EMAIL PROTECTED]>:
>
> have a database behind a firewall ... we'd like to make connections
> available to that machine through a machine outside of the firewall, so
> that its a secure connection to the "proxy", and in-secure from
> proxy->database ...
>
> the 'clie
22 matches
Mail list logo
