Re: JDBC changes for 7.2... some questions...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Actually, it's not a new function on the server... I'm just trying to find a
way to access the getInsertedOID() method in the statement object without
having direct access to the statement object. (My use-case is when the JDBC
driver is wrapped in a pooling manager, like PoolMan, it wraps all classes.)

I wanted to catch the line 'select @@last_oid' which would return a result set
with the single entry based on the results of the method call 'getInsertedOID'
but some people didn't like the syntax. So, I'm seaking comments to see if
there is a better syntax people like, as long as they don't mind the
functionality. One option is the 'faking' of the function call on the server,
which really isn't a good option in itself, but outside of my original 'catch'
line, its all I got.

What's your thoughts? Do you see the need for the functionality? Do you have
a solution that I need?

On 22-Aug-2001 Barry Lind wrote:
> I am assuming that this would be a new function in the server.
> Therefore this wouldn't be jdbc specific and would be available to all
> client interfaces. I don't see what this really has to do with JDBC.
>
> thanks,
> --Barry
>
> Ned Wolpert wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>> Ok, so you're not opposed to the idea then, just the syntax. Does anyone
>> oppose having this concept in the JDBC driver? And what syntax is
>> acceptable?
>> Could we just do
>> 'select getInsertedOID()'
>> which would break people who have functions called getInsertedOID() of
>> course...
>>
>>
>>
>> On 21-Aug-2001 Tom Lane wrote:
>>
>>>Ned Wolpert <ned(dot)wolpert(at)knowledgenet(dot)com> writes:
>>>
>>>>What about the 'select @@last_oid' to make the getInsertedOID() call
>>>>available even when the driver is wrapped by a pooling manager?
>>>>
>>>>How do people feel about this?
>>>>
>>>Yech. At least, not with *that* syntax. @@ is a valid operator name
>>>in Postgres.
>>>
>>> regards, tom lane
>>>
>>>---------------------------(end of broadcast)---------------------------
>>>TIP 5: Have you checked our extensive FAQ?
>>>
>>>http://www.postgresql.org/users-lounge/docs/faq.html
>>>
>>
>>
>> Virtually,
>> Ned Wolpert <ned(dot)wolpert(at)knowledgenet(dot)com>
>>
>> D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.0.6 (GNU/Linux)
>> Comment: For info see http://www.gnupg.org
>>
>> iD8DBQE7gv5yiysnOdCML0URAq7qAJkBRhAcE9wctn7bUAv7UMwN3n9+nwCeJR4V
>> ymYTw8l3f9WU4V5idFsibAE=
>> =UQ2M
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 2: you can get off all lists at once with the unregister command
>> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>>
>>

Virtually,
Ned Wolpert <ned(dot)wolpert(at)knowledgenet(dot)com>

D08C2F45: 28E7 56CB 58AC C622 5A51 3C42 8B2B 2739 D08C 2F45
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7g+agiysnOdCML0URAvbvAJ9GO/spmwQYZessjk4IenhtPuguSwCdHRQN
xH+tnGqKpmg/UOSnxOevek0=
=pcr+
-----END PGP SIGNATURE-----