diff options
author | Bruce Momjian <bruce@momjian.us> | 2001-09-06 20:43:39 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2001-09-06 20:43:39 +0000 |
commit | 0059c4216c1e106311cd935dee2b9c42d9a7a1d3 (patch) | |
tree | d3ca5f4afe6a0f2c610f53ff915caa5367f6c30a /src/backend/executor/execProcnode.c | |
parent | 1fbb2d9cc85df97f8c4c71a49d4068973904fc60 (diff) | |
download | postgresql-0059c4216c1e106311cd935dee2b9c42d9a7a1d3.tar.gz postgresql-0059c4216c1e106311cd935dee2b9c42d9a7a1d3.zip |
>Well, if it is that easy, I can do it. Patch attached and applied.
>
>> On Mon, 3 Sep 2001 22:01:17 -0500, you wrote:
>> public boolean isWritable(int column) throws SQLException
>> {
>> return !isReadOnly(column);
>> }
Actually, I think this change has a consequence for this method
in the same class:
public boolean isDefinitelyWritable(int column)
throws SQLException
{
return isWritable(column);
}
This is from the JDBC spec
(http://java.sun.com/j2se/1.3/docs/api/java/sql/ResultSetMetaData.html):
isReadOnly() - Indicates whether the designated column is
definitely not writable.
isWritable() - Indicates whether it is possible for a write on
the designated column to succeed.
isDefinitelyWritable() - Indicates whether a write on the
designated column will definitely succeed.
At this time we don't really implement the fine semantics of
these methods. I would suggest the following defaults:
isReadOnly() false
isWritable() true
isDefinitelyWritable() false
And that would mean that your patch is correct, but
isDefinitelyWritable() would need to be patched accordingly:
public boolean isDefinitelyWritable(int column)
throws SQLException
{
return false;
}
Again, both in jdbc1 and jdbc2.
Regards,
Ren? Pijlman <rene@lab.applinet.nl>
Diffstat (limited to 'src/backend/executor/execProcnode.c')
0 files changed, 0 insertions, 0 deletions