On Mon, 11 Jun 2012, Dean Schulze wrote:
> Out of curiosity why didn't the driver map the Postgresql UUID to a Java
> UUID?
>
The example I gave of calling getString must return a String and not
another type. With a recent JDBC Driver and Java version, calling
getObject will return a UUID o
Thanks.
Out of curiosity why didn't the driver map the Postgresql UUID to a Java
UUID?
On 6/6/12 2:12 AM, "Kris Jurka" wrote:
>
>
>On Tue, 5 Jun 2012, Dean Schulze wrote:
>
>>
>> I'm using Hibernate (3.6 and 4.0) with Postgresql 9.1. Our tables have
>> UUIDs in them and your driver is tryin
On Tue, 5 Jun 2012, Dean Schulze wrote:
>
> I'm using Hibernate (3.6 and 4.0) with Postgresql 9.1. Our tables have
> UUIDs in them and your driver is trying to convert UUIDs to longs:
>
This is a hibernate mapping problem, not a JDBC Driver problem. If you
have a plain ResultSet and call g
I'm using Hibernate (3.6 and 4.0) with Postgresql 9.1. Our tables have UUIDs
in them and your driver is trying to convert UUIDs to longs:
Caused by: org.postgresql.util.PSQLException: Bad value for type long :
dbada1e4-a165-4601-b34e-d08428cd81df
at
org.postgresql.jdbc2.AbstractJdbc2ResultS
Il 04/08/2011 13.00, Oliver Jowett ha scritto:
2011/8/4 Silvio Brandani:
On the Tomcat side we get followin message:
Caused by: java.io.IOException: Tried to send an out-of-range integer as a
2-byte value: 34027
at org.postgresql.core.PGStream.SendInteger2(PGStream.java:201)
at
org.postgresql
2011/8/4 Silvio Brandani :
> On the Tomcat side we get followin message:
>
>
> Caused by: java.io.IOException: Tried to send an out-of-range integer as a
> 2-byte value: 34027
> at org.postgresql.core.PGStream.SendInteger2(PGStream.java:201)
> at
> org.postgresql.core.v3.QueryExecutorImpl.sendPars
On Wed, Apr 13, 2011 at 6:52 AM, Donald Fraser wrote:
>> If the server is shut down mid-query, doesn't the backend complete the
>> current query cycle before closing the connection?
>> i.e. we'd see ErrorResponse, ReadyForQuery, and return control to the
>> app before seeing EOF anyway?
>> The pro
From: "Oliver Jowett"
If the server is shut down mid-query, doesn't the backend complete the
current query cycle before closing the connection?
i.e. we'd see ErrorResponse, ReadyForQuery, and return control to the
app before seeing EOF anyway?
The protocol spec is a bit vague there.
From an o
Saneesh Apte wrote:
I think I found two bugs (and I hope I am not wasting everyone's time).
One is minor: the base type of a boolean[] is java.sql.Types.BIT
instead or java.sql.Types.BOOLEAN. At the very least shouldn't these be
aliases for the same type?
Types.BOOLEAN does not exis
Hi,
I think I found two bugs (and I hope I am not wasting everyone's
time).
One is minor: the base type of a boolean[] is java.sql.Types.BIT
instead or java.sql.Types.BOOLEAN. At the very least shouldn't these
be aliases for the same type?
And secondly the returned type from a s
On Mon, 28 Jun 2010, Saneesh Apte wrote:
One is minor: the base type of a boolean[] is java.sql.Types.BIT
instead or java.sql.Types.BOOLEAN. At the very least shouldn't these be
aliases for the same type?
These are aliases for the same type. I believe we accept either BOOLEAN
or BIT as
Saneesh Apte wrote:
> the base type of a boolean[] is java.sql.Types.BIT instead or
> java.sql.Types.BOOLEAN. At the very least shouldn't these be
> aliases for the same type?
>
> And secondly the returned type from a smallint[] is an Integer[]
> instead of a Short[].
Should the objects in
Hi,
I think I found two bugs (and I hope I am not wasting everyone's time).
One is minor: the base type of a boolean[] is java.sql.Types.BIT instead or
java.sql.Types.BOOLEAN. At the very least shouldn't these be aliases for
the same type?
And secondly the returned type from a smal
On Sat, 18 Aug 2007, Otto Weichselbaum wrote:
While using views calling functions on INSERT, UPDATE and DELETE via
according rules, I noticed an inconsistent behaviour of the
JDBC-interface of postgres;
an INSERT-, UPDATE- or DELETE-statement producing tuples as return-value
(in our case thro
Dear Ladies and Gentlemen,
I do not know if this can even be considered a bug, but I would be
pleased, if somebody could make a statement on this:
environment:
PostgreSQL 8.1 and 8.2
Redhat and WinXP
While using views calling functions on INSERT, UPDATE and DELETE via
according rules,
On Wed, 8 Nov 2006, David Green wrote:
the JDBC driver does not handle setNull for boolean types.
the switch statement in setNull should be expanded with a case that
checks for Types.BOOLEAN
The JDBC2 driver does not handle Types.BOOLEAN because that was added in
JDBC3. See org.postgresq
the JDBC driver does
not handle setNull for boolean types.
the switch statement
in setNull should be expanded with a case that checks for
Types.BOOLEAN
On Mon, 1 Aug 2005, Andrus Adamchik wrote:
> Just tested it with build 312 and the original problem went away. Now
> I am seeing a new problem with null BLOBs only:
>
> java.sql.SQLException: ERROR: column "blob_col" is of type bytea but
> expression is of type oid
bytea is not the correct
On Thu, 14 Apr 2005, Xavier Maysonnave wrote:
> postgresql-8.0-311.jdbc3.jar
>
> While analysing the index structures of a metadata table with the
> following statement :
>
> ResultSet parts = dbMeta.getIndexInfo("aCatalog", "aMetaSchema",
> "aTable", false, false);
> ...
> if (parts != null
Hi,
Environment :
Windows XP SP2
Postgres 8.0
JDK 1.5.0_02
postgresql-8.0-311.jdbc3.jar
While analysing the index structures of a metadata table with the
following statement :
ResultSet parts = dbMeta.getIndexInfo("aCatalog", "aMetaSchema",
"aTable", false, false);
...
if (parts != null) {
tr
On Sun, 7 Nov 2004, Federico Fissore wrote:
> As subject, i got a stored function that returns an int2 i successfully
> call it using a callable statement, exactly as it is written in the
> manual, but when the getShort expression is executed, i receive a
> "Exception in thread Exception in thre
i forgot :)
executing the function manually leads to no errors
> Da: "Federico Fissore" <[EMAIL PROTECTED]>
> Data: Sun, 07 Nov 2004 17:54:47 +
> A: [EMAIL PROTECTED]
> Oggetto: [BUGS] JDBC driver. Class Cast Exception when calling
> CallableStatement.getShort
As subject, i got a stored function that returns an int2
i successfully call it using a callable statement, exactly as it is written in
the manual, but when the getShort expression is executed, i receive a
"Exception in thread Exception in thread "Timer-1"
java.lang.ClassCastException: java.lang
kris,
Next you can see how the same test-case is handled by DB2.
-- IBM DB2 V6.1 for Linux
CREATE TABLE userid.t (
f1 numeric(6,3),
f2 numeric(6,4),
f3 numeric(8,2)
);
create view userid.v as
select
(f1+f2+f3) as fsum,
coalesce(f1,f2,f3) as fcoal,
(f1*f2*f3) as fprod,
(f1/f2) as fdiv
I have found that the problem is worst.
In the sample adjunct, you can see that error arise at the time when
the view's sql text is parsed and saved in database catalog.
Then generic NUMERIC type is forced for every calculated column without
regard or precision.
And at execute time the f2 colu
Stephan Szabo wrote:
On Sun, 4 Jul 2004, Kris Jurka wrote:
On Sat, 3 Jul 2004, Dario V. Fassi wrote:
In the sample adjunct, you can see that error arise at the time when the
view's sql text is parsed and saved in database catalog.
Then generic NUMERIC type is fo
Stephan, look at the samples I send in previous posts , from PgSql and
Db2.
I know it's a no ease task to change all that behavior , but you must
agree that a Numeric column with the fractional part varing from row to
row are different data types and break relational rules.
If this is the case
On Sun, 4 Jul 2004, Dario V. Fassi wrote:
> Stephan, look at the samples I send in previous posts , from PgSql and Db2.
I don't see any samples apart from the original view descriptions and the
getColumns results. I see some implication about db2 but no details. My
guess is that the messages a
On Sun, 4 Jul 2004, Dario V. Fassi wrote:
>
>
> Stephan Szabo wrote:
>
> >On Sun, 4 Jul 2004, Kris Jurka wrote:
> >
> >
> >
> >>On Sat, 3 Jul 2004, Dario V. Fassi wrote:
> >>
> >>
> >>
> >>>In the sample adjunct, you can see that error arise at the time when the
> >>>view's sql text is parsed and
On Sun, 4 Jul 2004, Kris Jurka wrote:
> On Sat, 3 Jul 2004, Dario V. Fassi wrote:
>
> > In the sample adjunct, you can see that error arise at the time when the
> > view's sql text is parsed and saved in database catalog.
> > Then generic NUMERIC type is forced for every calculated column without
On Sat, 3 Jul 2004, Dario V. Fassi wrote:
> In the sample adjunct, you can see that error arise at the time when the
> view's sql text is parsed and saved in database catalog.
> Then generic NUMERIC type is forced for every calculated column without
> regard or precision.
> And at execute time
On Fri, 9 Jan 2004, Jonathan Purvis wrote:
> The JDBC driver that ships with PostgreSQL 7.4.1 doesn't insert floats
> of value NaN. As it uses Float.toString(x) to convert the value for
> insertion into the database, it tries to insert NaN instead of 'NaN' and
> gets the error "Attribute 'nan'
The JDBC driver that ships with PostgreSQL 7.4.1 doesn't insert floats
of value NaN. As it uses Float.toString(x) to convert the value for
insertion into the database, it tries to insert NaN instead of 'NaN' and
gets the error "Attribute 'nan' not found". The same bug occurs for
doubles and w
is Foti; [EMAIL PROTECTED]
> Subject: Re: [BUGS] Jdbc connection pooling and PG 7.4 consistently
> fails
>
>
>
>
> On Fri, 19 Dec 2003, Lamar Owen wrote:
>
> > On Friday 19 December 2003 01:27 pm, Kris Jurka wrote:
> > > The RPMs do not have the correct
a [mailto:[EMAIL PROTECTED]
> Sent: 19 December 2003 22:10
> To: Lamar Owen
> Cc: Lewis Foti; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [BUGS] Jdbc connection pooling and PG 7.4 consistently
> fails
>
>
>
>
> On Fri, 19 Dec 2003, Lamar Owen wrote:
>
> >
>
On Fri, 19 Dec 2003, Lamar Owen wrote:
>
> While I've got your attention on this, where is a good place for the RPM to
> place the jars that would be usable by the largest number of people?
> Currently they are just plunked down and no real installation is being done.
>
> Or, to put it a differe
On Friday 19 December 2003 04:11 pm, Kris Jurka wrote:
> On Fri, 19 Dec 2003, Lamar Owen wrote:
> > On Friday 19 December 2003 01:27 pm, Kris Jurka wrote:
> > > The RPMs do not have the correct jar file. Try one of those available
> > > from http://jdbc.postgresql.org/download.html
> > At the tim
On Fri, 19 Dec 2003, Lamar Owen wrote:
> On Friday 19 December 2003 01:27 pm, Kris Jurka wrote:
> > The RPMs do not have the correct jar file. Try one of those available
> > from http://jdbc.postgresql.org/download.html
>
> At the time I put the RPMs together there were no 'stable' 7.4 jars, so
On Friday 19 December 2003 01:27 pm, Kris Jurka wrote:
> The RPMs do not have the correct jar file. Try one of those available
> from http://jdbc.postgresql.org/download.html
At the time I put the RPMs together there were no 'stable' 7.4 jars, so I
grabbed the dev jars and the 7.3 jars and packa
On Thu, 18 Dec 2003, Lewis Foti wrote:
> Hi
>
> Having downloaded and installed the rpms for 7.4 I upgraded the database and
> began testing. As the system under development is based on servlets we are
> using the JDBC3 Jdbc3PoolingDataSource to provide the connections. All
> attempts to read fro
Hi
Having downloaded
and installed the rpms for 7.4 I upgraded the database and began testing. As the
system under development is based on servlets we are using the JDBC3
Jdbc3PoolingDataSource to provide the connections. All attempts to read from the
database via jdbc pooled connections n
Patch Applied,
Thanks,
Dave
On Mon, 2003-11-03 at 05:25, Kris Jurka wrote:
> On Fri, 15 Aug 2003, Richard Froud wrote:
>
> > Please enter a FULL description of your problem:
> >
> > When reading database metadata for foreign keys using the JDBC
>
On Fri, 15 Aug 2003, Richard Froud wrote:
> Please enter a FULL description of your problem:
>
> When reading database metadata for foreign keys using the JDBC
> DatabaseMetaData.getImportedKeys() and DatabaseMetaData.getExportedKeys()
> methods t
POSTGRESQL BUG REPORT TEMPLATE
Your name : Richard Froud
Your email address : [EMAIL PROTECTED]
S
POSTGRESQL BUG REPORT TEMPLATE
Your name : Christopher Marshall
Your email address : [EMAIL PROTECTED]
Sys
I would highly recommend using either
1) blackdown j2sdk1.4.1
2) SUN j2sdk1.4.1 (based on blackdown, but the former always runs better!)
(BTW, after testing my app set to freebsd 5.1, native jdk1.4.1 runs nice
too these days).
GCJ is not that much tested IMO, and they are *UNLIKELY* to
provide
I am running a Java
application on Linux which connects to the Postgresql on Linux using jdbcodbc
bridge.
But this is the
error I am getting :
sun.jdbc.odbc.JdbcOdbcDriverjava.lang.ClassNotFoundException:
sun.jdbc.odbc.JdbcOdbcDriver at 0x4028115f:
java.lang.Throwable.Throwable(java.l
The optimization added in
src/interfaces/jdbc/org/postgresql/core/Encoding.java
version 1.7 breaks JDBC since it is not thread safe.
The new method decodeUTF8() uses a static (i.e. class member)
but is synchronized on the instance so it won't work with multiple
instances used in parallel by multi
Your name : Gregory Faruch
Your email address : [EMAIL PROTECTED]
System Configuration
-
Architecture (example: Intel Pentium) : Sparc
Operating System (example: Linux 2.0.26 ELF) : Solaris 2.9
PostgreSQL version (example: PostgreSQL-7.1.1)
This code doesn't exist in the jdbc driver anymore. They must have
already fixed it.
---
Dmitry Tkach wrote:
> The attached patch fixes 'Bad Timestamp format' exception when timestamp value is
>'ininity' or '-ininity'.
>
The attached patch fixes 'Bad Timestamp format' exception when timestamp value is
'ininity' or '-ininity'.
I hope, it helps...
Dima.
Index: AbstractJdbc1ResultSet.java
===
RCS file:
/projects/cvsroot/pgsql/src/interfaces/jdbc/org/
Dear JDBC team,
I'm using pgjdbc2.jar from february and facing this problem:
I have a table (UNICODE database is set up) having numeric type in it.
Than something like this:
statement = connection.preparedStatement( "SELECT * from account WHERE
rate > ?" );
statement.setBigDecimal( 1, BigDecimal
I'm using the PostgreSQL 7.2.1 server and JDBC drivers distributed
with Red Hat 7.3. When I create a series of tables and foreign keys, and
then use the JDBC DatabaseMetaData calls getImportedKeys and
getExportedKeys, the results are incorrect. In some cases, I get the
primary key table
Not strictly a bug, but I have added the stub methods to
the JDBC driver to permit compilation with the 1.4.0 JDK.
Note this is not an implementation of the new functionality, it
merely returns false or throws NotImplemented exceptions, but
at least it all compiles.
I did this when 1.4.0 was in b
Hello,I got some pb with this configuration
database pgsql 7.1 and connect with jdbc driver from 7.2
I notice something that could be a jdbc bugs :when
connection is not set to autocommit (setAutocommit(false))When you catch an
exception, the next requests until the next commit are totaly ing
I'm also having problems with Postgres' JDBC driver and the tag
libraries. I have a JSP page which selects everything from a table, and
prints it out.
Workaround: back up to using "jdbc7.0-1.2.jar" (or "pgjdbc1.jar", if
you don't need all the Java2 JDBC stuff.)
jdbc7.1-1.2.jar - fet
Using the JDBC interface to inspect the metadata in a table, the
ResultSet returned from using DatabaseMetaData.getImportedKeys
includes values for KEY_SEQ. This is an integer value and in the
case of Postgreql starts at zero.
I can find no formal definition of where this value should start
but
i am seeing postgre 6.4 return the following error message when performing
a JDBC update with executeUpdate(). any ideas what it means?
ava.sql.SQLException: results returned
at java.lang.Throwable.(Compiled Code)
at java.lang.Exception.(Compiled Code)
at java.sql.SQLExce
Hi,
I'm running Postgresql 7.1.2 server on RedHat Linux
7.1 (intel) and connecting using JDBC on Windows NT using
jdbc7.1-1.2.jar.
The sequence to reproduce the error is as
follows:
1. Create database with various constraints (such
as UNIQUE, CHECK, etc).
2. Queue 3 or more INSERT / UP
Please get newest jdbc driver at:
http://jdbc.fastcrypt.com
> Your name : Hatanaka, Akihiro
> Your email address : [EMAIL PROTECTED]
>
>
> System Configuration
> -
> Architecture (example: Intel Pentium) : Intel Pentium
>
> Operatin
Hi,
I'm making some code handling several kinds of files as large object. I found the
JDBC driver returned without finish reading the file. I made the test program
named lobtest.java, which is added at the end of this mail.
This test program read a file (default is "tomcat.gif" which is fetched
Original Message -
From: "Akira Kumakiri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, August 18, 2001 6:55 PM
Subject: [BUGS] JDBC Large Object getBinaryStream returns -1 before EOF
> Hi,
>
> I'm making some code handling several kinds o
Hi,
I'm making some code handling several kinds of files as large object. I found the
JDBC driver returned without finish reading the file. I made the test program
named lobtest.java, which is added at the end of this mail.
This test program read a file (default is "tomcat.gif" which is fetched
Bjorn Peterson ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC driver converts search string patterns to lowercase
Long Description
The metadata class of the Postgresql 7.1 JDBC driver converts search string patterns
to a
Download newer version at:
http://jdbc.fastcrypt.com
This bug is fixed.
> Dave Antal ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> JDBC - DatabaseMetaData.getTables() null pointer exception
>
> Long Descri
Dave Antal ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC - DatabaseMetaData.getTables() null pointer exception
Long Description
When you pass the DatabaseMetaData.getTables() method a types array that contains
"VIEW" a
Denis ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC: The raise of an SQLException force the user to call either commit() or
rollback() on the connection
Long Description
Using JDBC, after an SQLException is raised as a
> Kenny GONG ([EMAIL PROTECTED]) reports a bug with a severity of 1
> The lower the number the more severe it is.
>
> Short Description
> JDBC 7.0-1.2.jar has limit of 8k!
You need the 7.1 JAR file.
>
> Long Description
> when i insert a row data more than 8k into PostgreSQL7.1, jdbc throw m
Kenny GONG ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
JDBC 7.0-1.2.jar has limit of 8k!
Long Description
when i insert a row data more than 8k into PostgreSQL7.1, jdbc throw me a exception
called "SQL statement too long."
Hi,
Here are the maximum information about the error:
OS where the class is running: winnt4 with jdk1.3
DB OS: Linux Debian potatoe
Postgresql version: 7.0.3
Driver JDBC: included in the source code.
Description:
---
First case (postmaster is running ok):
I get the connection with:
co
Dave Cramer ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC setObject(n,obj) throws exception when obj is null
Long Description
The jdbc call setObject(n,obj) does not set the column to null if the object is null
and the
Quoting [EMAIL PROTECTED]:
>
> We are running a PostgreSQL server on a Debian 2.2 and we have problems
> with
> the
> mothod getTimestamp() of the ResultSet class;
> we have find that if we insert a timestamp on a table, for example
> '2000-10-09 12:21:34.321+01'
> when we try to read that tuple
We are running a PostgreSQL server on a Debian 2.2 and we have problems with
the
mothod getTimestamp() of the ResultSet class;
we have find that if we insert a timestamp on a table, for example
'2000-10-09 12:21:34.321+01'
when we try to read that tuples using the JDBC driver we have an exception
Patrice Le Gurun ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC packaging error in 7.0.3 with RPM
Long Description
I had recently a bug in my Java application. I got a ResultSet from a request to the
DB and I had to go t
Hi,
While trying 7.1b4 I got this using JDBC2:
ERROR: A request from 10.0.0.46 (10.0.0.46) resulted in
java.lang.NumberFormatException: 20 18:46:53+09
java.lang.NumberFormatException: 20 18:46:53+09
at java.lang.Integer.parseInt(Integer.java, Compiled Code)
at java.lang.Integ
Hi all,
I already reported this directly to Peter Mount but since I have since
joined this list I thought I should make it a more wide-spread report.
The issue is that if you use getDate() on a field that is a timestamp type
then you will get an SQLException that wraps a NumberFor
POSTGRESQL BUG REPORT TEMPLATE
Your name : Jered Floyd
Your email address : [EMAIL PROT
POSTGRESQL BUG REPORT TEMPLATE
Your name : Jered Floyd
Your email address : [EMAIL PROT
At 00:01 02/02/01 -0500, [EMAIL PROTECTED] wrote:
>John Lemcke ([EMAIL PROTECTED]) reports a bug with a severity of 2
>The lower the number the more severe it is.
>
>Short Description
>JDBC ResultSet.getObject() fails for type INTERVAL
>
>Long Description
>Trying to retrieve an INTERVAL from a Res
John Lemcke ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC ResultSet.getObject() fails for type INTERVAL
Long Description
Trying to retrieve an INTERVAL from a ResultSet causes an exception. The following
output is from
This is no longer a problem in 7.1. The bug here was the same one
introduced by the wrong version of Gunner's bytearray pooling patch
being applied. It was fixed in current sources by Peter commenting out
the bytearray pooling.
thanks,
--Barry
Bruce Momjian wrote:
>
> Anyone fixing this bug?
I think this is fixed in 7.1beta.
> Alexander Dietrich ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> JDBC driver throws SQLException while parsing timestamp
>
> Long Description
> Hi,
>
> there's a discrepancy betwe
Quoting Barry Lind <[EMAIL PROTECTED]>:
> This is no longer a problem in 7.1. The bug here was the same one
> introduced by the wrong version of Gunner's bytearray pooling patch
> being applied. It was fixed in current sources by Peter commenting out
> the bytearray pooling.
That's what I thou
Quoting Bruce Momjian <[EMAIL PROTECTED]>:
>
> Anyone fixing this bug?
>
> > I reported a JDBC bug in the 7.1 beta1 release back in December and
> notice that the same bug is still present in the current beta 3 sources.
> The problem relates to nested cursors failing and is quite simple to
> r
Alexander Dietrich ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC driver throws SQLException while parsing timestamp
Long Description
Hi,
there's a discrepancy between PreparedStatement.setTimestamp() and
ResultSet.getTi
Anyone fixing this bug?
> I reported a JDBC bug in the 7.1 beta1 release back in December and notice that the
>same bug is still present in the current beta 3 sources. The problem relates to
>nested cursors failing and is quite simple to reproduce. A simple test case can be
>found at:
>
>
I reported a JDBC bug in the 7.1 beta1 release back in December and notice that the
same bug is still present in the current beta 3 sources. The problem relates to
nested cursors failing and is quite simple to reproduce. A simple test case can be
found at:
http://www.twospuds.com/pg7-1b3-jdb
Sorry for the delay.
What is the setting in pg_hba.conf? It sounds like this is set to trust
which would produce this affect.
Peter
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, December 16, 2000 4:04 AM
Subject: [BUGS]
Can you please try the current beta from our ftp site. I think this is
fixed in 7.1beta.
> Jason Southern ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> JDBC PreparedStatement.setMaxRows() affects other objects intan
Jason Southern ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC PreparedStatement.setMaxRows() affects other objects intantiated from this class
and it's parent class
Long Description
==
Problem:
If try to use field of type "java.sql.Types.BIT" obtains error "Unknown
Types Value"
Resolution:
Add this:
PreparedStatement.java
460,461d459
< case Types.BIT:
< set(parameterIndex,
((Boolean)x).booleanValue()
Jason Southern ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC Connection must be restarted after executing SQL statement that calls a PL/PGSQL
function that won't compile
Long Description
[EMAIL PROTECTED] wrote:
> If the userid is valid, even though null password or wrong password is sent to
>server with JDBC Driver, the authentication still pass!
> What is a terrible bug!
Check ~postgres/data/pg_hba.conf
By default AuthenticationType for localhost connections is TRUST. You
hav
Cheeren Shieh ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC Driver Authentication Bug
Long Description
If the userid is valid, even though null password or wrong password is sent to server
with JDBC Driver, the authent
andre levy ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC: connection.isClosed() doesnt throw exception
Long Description
connection.isClosed() doesn't throw an SQLException if "a database access error
occurs". (cf
http:
Hello postgresql team,
I'am trying to connect to the posgresql database through JDBC and it
doesn't function.
1. I have made the postgresql.jar through the command "make jdbc2" -as
it is described in /src/interfaces/jdbc/ source- and it is copied to my
CLASSPATH
2. I have an access to the datab
Dave Barnett ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC driver DatabaseMetaData.getTables() unconditionally lowercases tableName pattern
Long Description
According to Chapter 2 of the User's Guide, NAMES may be quoted
Jan Thomae ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
JDBC-Driver produces wrong output.
Long Description
Hi,
I recently downloaded the last snapshot of PostgreSQL and also the newest JDBC-Driver
for it. I played a bit a
On Mon, 16 Oct 2000, Alexander Yurov wrote:
> 1. JDBC Driver returns empty separator in the database catalog.
In the source I have the following comment:
// PM Sep 29 97 - changed from "." as we don't support catalogs.
So back in 1997 I removed the "."
> 2. Why JDBC Driver returns column (proc
1. JDBC Driver returns empty separator in the database catalog.
2. Why JDBC Driver returns column (procedures etc.) name pattern in lower case?
Al
1 - 100 of 103 matches
Mail list logo
