Hi all.
He's right. The DatabaseMetaData.getExportedKeys() method is
simply not yet implemented, both in the jdb1 and the jdbc2
driver. Its open for development.
If someone can write the query on the system catalogs I'll be
glad to implement the Java code and a test case. The
hello,
i think there's a simple error in the isWritable method of the
ResultSetMetaData class in the jdbc2 postgresql driver. the isWritable method
looks like this:
public boolean isWritable(int column) throws SQLException
{
if (isReadOnly(column))
return true;
Hello.
I have been having problems with postgresql large objects...i have been
searching the archives of this group and i have posted a question or two but
i have so far be unable to resolve the issues. right now, i have a screen
that loads a few LOs...they occasionally don't make it to the
* Keve Mller [EMAIL PROTECTED] wrote:
|
| An initial version for get(Imported|Exported)Keys and getCrossReference is
| available in jxDBCon (http://jxbdcon.sf.net) the file can be extracted
Do you only concentrate on compliance or is performance important as well ?
Have you done any performance
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
Hmmm, after a little more testing, I fixed a problem with backslashes.
New code attached.
Tom.
On Thu, Aug 30, 2001
Hi Bruce,
I guess that wasn't exactly a patch that I sent in but rather a test
program with the new routine embeded so that other people could try
it out easily.
I'll mail in the patch later. I'm a little distracted right now with
something else. For the moment just delete the patch that you
Patch removed at request of author. Will resubmit.
Hmmm, after a little more testing, I fixed a problem with backslashes.
New code attached.
Tom.
On Thu, Aug 30, 2001 at 11:46:16AM +0900, Thomas O'Dowd wrote:
Hi all,
I found some time this morning to write and test a new
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
The first one considered everything changed ?
I also fixed the rollback method in this one, assuming it was broken the
To all those who responded ,
Thanks for your response,
I have attached the test programs that I used in the form of text files. The
contents should be self evident. Please have a look and comment.
I used j2sdk1.3.1 down load to linux machine from sun.com as my java platform
and
And perl,
Barry Lind a écrit :
Kovács Péter wrote:
the driver what character set the backend is sending us? Can't
it ask the backend dynamically?
This is what it actually does, isn't it? (Based on what I usually see in the
trace output on the backend.) I tested a unicode database with
Alexander,
You have to set the encoding when you make the connection.
Properties props = new Properties();
props.put(user,user);
props.put(password,password);
props.put(charSet,encoding);
Connection con = DriverManager.getConnection(url,props);
where encoding is the proper encoding for your
Perhaps this is a silly question, but why do we have separate
JDBC 1 and 2 drivers?
Isn't the JDBC 2 driver also an implementation of JDBC 1?
Regards,
René Pijlman [EMAIL PROTECTED]
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
I suggest that the JDBC driver adopt PostgreSQL's indentation standards
(see PostgreSQL developers FAQ, question 1). I see that some source
files have used this standard, but the vast majority do not. We should
have a standard for consistency and our own sanity if nothing else.
Liam
--
Liam
hello. yet another follow-on to my questions...is there a way to determine
whether i am going to get this NOTICE before i execute a query? check
some status code or something?
thanks
chris
-Original Message-
From: Chris Markiewicz [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September
I suggest that the JDBC driver adopt PostgreSQL's indentation standards
(see PostgreSQL developers FAQ, question 1). I see that some source
files have used this standard, but the vast majority do not. We should
have a standard for consistency and our own sanity if nothing else.
Glad
I agree that this is needed. In fact I know Bruce wants to do something
in this area. In fact he sent out a few months ago a sample of the code
after it had been cleaned up by some tool. At the time no one seemed to
be very interested. Going forward for 7.2 I think now is the time that
Here is a revised patch with Barry's suggestions implemented
Dave
Index: Connection.java
===
RCS file:
/home/projects/pgsql/cvsroot/pgsql/src/interfaces/jdbc/org/postgresql/Connection.java,v
retrieving revision 1.26
diff -c
Yes, it is, but many of the libraries, and methods which are used in
version 2 of the driver aren't available in jdk1 so it won't compile or
run.
Dave
On Tue, 2001-09-04 at 12:50, Rene Pijlman wrote:
Perhaps this is a silly question, but why do we have separate
JDBC 1 and 2 drivers?
Isn't
On Tue, 28 Aug 2001, Bhuvaneswari wrote:
hi,
I am getting the following error while doing vacuumdb,
ERROR: mdopen: couldn't open test1: No such file or directory
vacuumdb: database vacuum failed on db1.
We got this error a lot in 6.5. Usually it means your table has somehow
been
Shaun Thomas wrote:
On Tue, 28 Aug 2001, Bhuvaneswari wrote:
hi,
I am getting the following error while doing vacuumdb,
ERROR: mdopen: couldn't open test1: No such file or directory
vacuumdb: database vacuum failed on db1.
We got this error a lot in 6.5. Usually it means your
On Tue, Sep 04, 2001 at 12:43:21PM -0700, Barry Lind wrote:
snip
I am OK with the style used for the C code. However I would like the
following additional step done for the java code: replace all tabs with
spaces.
Oh noo! Barry's stumbled over the tripwire of the Tab/Spaces
Just some minor fixes to avoid duplicate function calls that were bugging me.
If rows is garunteed not to change then we can store the size in a final class
variable,
but I wasn't sure I could assume that.
*** ResultSet.java.orig Tue Sep 4 16:34:14 2001
--- ResultSet.java Tue Sep 4
Barry Lind [EMAIL PROTECTED] writes:
I am OK with the style used for the C code. However I would like the
following additional step done for the java code: replace all tabs with
spaces.
I disagree with this, because then we are *not* applying the same coding
standards in the backend and
[forwarding to pgsql-hackers and Bruce as Todo list maintainer,
see comment below]
[insert with JDBC converts Latin-1 umlaut to ?]
On 04 Sep 2001 09:54:27 -0400, Dave Cramer wrote:
You have to set the encoding when you make the connection.
Properties props = new Properties();
Rene,
I would like to add one additional comment. In current sources the jdbc
driver detects (through a hack) that the server doesn't have multibyte
enabled and then ignores the SQL_ASCII return value and defaults to the
JVM's character set instead of using SQL_ASCII.
The problem boils down
Patch removed at Barry's request.
The first one considered everything changed ?
I also fixed the rollback method in this one, assuming it was broken the
same way
Dave
[ Attachment, skipping... ]
---(end of broadcast)---
TIP 1:
26 matches
Mail list logo