[BUGS] ResultSet.getTimestamp() Exception
Version: Postgresql 7.0.3-2 (RPM for RedHat6.2) JDBC Version: 7.0.3-2 (RPM for RedHat6.2) Java Version: Sun build 1.3.0 Calls to ResultSet.getTimestamp(...) throw an exception and report the following error: "Bad Timestamp Format at 19 in 2000-12-18 12:31:15.77-05" To reproduce: 1. Create a table using the TIMESTAMP SQL type. 2. Insert a row with a timestamp (using psql) 3. Use JDBC getTimestamp() For use, this bug is severe since it prevents us from using the timestamps in our EJB entity beans.
[BUGS] ResultSet.getTimestamp() Exception (UPDATE)
I downloaded the postgresql-7.0.3.tar.gz source and compiled the JDBC driver using make jdbc2, installed the new JAR file and it works now. There may be a problem in the RPM or something. Sorry that I can not be more specific. Thank you. Previously, I wrote: Version: Postgresql 7.0.3-2 (RPM for RedHat6.2) JDBC Version: 7.0.3-2 (RPM for RedHat6.2) Java Version: Sun build 1.3.0 Calls to ResultSet.getTimestamp(...) throw an exception and report the following error: "Bad Timestamp Format at 19 in 2000-12-18 12:31:15.77-05" To reproduce: 1. Create a table using the TIMESTAMP SQL type. 2. Insert a row with a timestamp (using psql) 3. Use JDBC getTimestamp() For use, this bug is severe since it prevents us from using the timestamps in our EJB entity beans.
Re: [BUGS] CConstraints using inherited attributes fail
[EMAIL PROTECTED] writes: > Unfortunately, PRIMARY KEY declarations applied to > my INHERIT()ed internal id attributes always fail. I believe this is fixed in current sources. regards, tom lane
Re: [BUGS] Backend dies when overloading + operator for bool
7.0.* and prior releases don't support using SQL-language functions as operators. 7.1 will. However, invoking three SQL queries to add two booleans sure seems like massive inefficiency... regards, tom lane
[BUGS] bug
Your name :Sandeep Joshi Your email address : [EMAIL PROTECTED] System Configuration - Architecture (example: Intel Pentium) : Intel Pentium Operating System (example: Linux 2.0.26 ELF) : Linux 2.2.16-3 PostgreSQL version (example: PostgreSQL-7.0): PostgreSQL-7.0.3 Compiler used (example: gcc 2.8.0) : egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) Please enter a FULL description of your problem: 1. If I kill postmaster then if I try to restart then I get errors saying it is already running. pg_ctl: It seems another postmaster is running. Try to start postmaster anyway. FATAL: StreamServerPort: bind() failed: Address already in use Is another postmaster already running on that port? If not, remove socket node (/tmp/.s.PGSQL.5432) and retry. /work/postgres/bin/postmaster: cannot create UNIX stream port pg_ctl: Cannot start postmaster. Is another postmaster is running? Please describe a way to repeat the problem. Please try to provide a concise reproducible example, if at all possible: -- pg_ctl start ps auxww | grep postmaster kill -9 $pid pg_ctl start If you know how this problem might be fixed, list the solution below: - pg_ctl should check whether the process and socket specified does exist or not.
