Re: bad timestamp confusion
Go to www.orionsupport.com and read about "using postgresql" (the link is somewhere in the EJB section I guess). use the database schema given there instead the one that comes with orion. That solved the problem on my machine. regard felix Eddie wrote: Just like other people in the newsgroup, I am receiving a bad timestamp error once in a while with Postgres 7.0. I looked in the newsgroup and saw some possible solutions, but I am a bit confused. How can I solve this problem for ever in case of a DateTime field ??? Someone talked about using java.sql.Date instead of java.util.Date, the other about getting the last postgres jdbc driver I got the last postgres driver from the postgres site, so what should I do ?? I was thinking about just using Strings to store Date format info. What about this ? And what should I do when I get such an error. Filling the database all over again helps. But what, when I have everyting ready online ?? Regards, Eddie -- Felix SchmidTech@Spree Software Technology GmbH mailto: [EMAIL PROTECTED] http://www.tech.spree.de/ http://www.techatspree.com tel.: ++49/30/235 520-38Blowstr. 66 fax.: ++49/30/236 318-7910783 Berlin (Aufgang D, 4.Etage)
RE: bad timestamp confusion; BUGje
Is this in a table you designed or are you letting orion create them? if the later you can change the descriptor to create the other type of field, if the later you could do a alter table... I had this problem before with postgresQL and that is how I got around it. Al -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eddie Sent: Thursday, March 22, 2001 4:06 PM To: Orion-Interest Subject: Re: bad timestamp confusion; BUGje Helllu there, Ok, I dit download the the latest jdbc driver source and compiled it. I still had te same error and changed the getTimestamp function, such that it works. The problem occurs with Postgres Date field (I have version 7.0), not with Postgres DateTime fields. The problem is as followes: The driver checks the date from postgres and looks for a + or - sign at the end of the string for the GMT offset. It also does that when it concerns a postgres Date field, which is the problem, as it shouldn't. It then encounters the - between the month and day and inserts the string GMT there - rubbish - Exception!!! Am I missing something here, or is this really a bug ? If it is, please change it in the following release. Goodluck, Eddie - Original Message - From: Jeff Schnitzer [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 8:08 PM Subject: RE: bad timestamp confusion Take a look at this message I posted in January: http://www.mail-archive.com/orion-interest@orionserver.com/msg08677.html If you patch the JDBC driver to read whatever format your dates are coming back as (you should see the actual formatted date string in the exception message), you should be ok. You might first check the CVS copy of the JDBC driver to see if it works; with any luck patches have already been made. Storing dates as strings just seems like a bad idea. It's nice to be able to do date math in SQL queries when you want to analyze your data. Jeff -Original Message- From: Eddie [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:55 AM To: Orion-Interest Subject: bad timestamp confusion Just like other people in the newsgroup, I am receiving a bad timestamp error once in a while with Postgres 7.0. I looked in the newsgroup and saw some possible solutions, but I am a bit confused. How can I solve this problem for ever in case of a DateTime field ??? Someone talked about using java.sql.Date instead of java.util.Date, the other about getting the last postgres jdbc driver I got the last postgres driver from the postgres site, so what should I do ?? I was thinking about just using Strings to store Date format info. What about this ? And what should I do when I get such an error. Filling the database all over again helps. But what, when I have everyting ready online ?? Regards, Eddie
RE: bad timestamp confusion
Take a look at this message I posted in January: http://www.mail-archive.com/orion-interest@orionserver.com/msg08677.html If you patch the JDBC driver to read whatever format your dates are coming back as (you should see the actual formatted date string in the exception message), you should be ok. You might first check the CVS copy of the JDBC driver to see if it works; with any luck patches have already been made. Storing dates as strings just seems like a bad idea. It's nice to be able to do date math in SQL queries when you want to analyze your data. Jeff -Original Message- From: Eddie [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:55 AM To: Orion-Interest Subject: bad timestamp confusion Just like other people in the newsgroup, I am receiving a bad timestamp error once in a while with Postgres 7.0. I looked in the newsgroup and saw some possible solutions, but I am a bit confused. How can I solve this problem for ever in case of a DateTime field ??? Someone talked about using java.sql.Date instead of java.util.Date, the other about getting the last postgres jdbc driver I got the last postgres driver from the postgres site, so what should I do ?? I was thinking about just using Strings to store Date format info. What about this ? And what should I do when I get such an error. Filling the database all over again helps. But what, when I have everyting ready online ?? Regards, Eddie
RE: bad timestamp confusion
The problem seemed to have gone away when I tried the PostgreSQL 7.1b5 driver. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Eddie Sent: Wednesday, March 21, 2001 4:55 AM To: Orion-Interest Subject: bad timestamp confusion Just like other people in the newsgroup, I am receiving a bad timestamp error once in a while with Postgres 7.0. I looked in the newsgroup and saw some possible solutions, but I am a bit confused. How can I solve this problem for ever in case of a DateTime field ??? Someone talked about using java.sql.Date instead of java.util.Date, the other about getting the last postgres jdbc driver I got the last postgres driver from the postgres site, so what should I do ?? I was thinking about just using Strings to store Date format info. What about this ? And what should I do when I get such an error. Filling the database all over again helps. But what, when I have everyting ready online ?? Regards, Eddie
Re: bad timestamp confusion
Thanks Jeff, H, I am a bit confused, again. I went searching for the correct postgres jdbc driver, and don't know exactly where to get the last version and source (I thought I did). I seached on http://jdbc.postgresql.org/download/ but is that the correct site ? and where can I get the source as I can't find it. I searched on http://www.postgresql.org/cgi/cvsweb.cgi/pgsql/src/interfaces/jdbc/, but there I only have a complete three and don't realy know what to download. Regards, Ed Bras - Original Message - From: Jeff Schnitzer [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 8:08 PM Subject: RE: bad timestamp confusion Take a look at this message I posted in January: http://www.mail-archive.com/orion-interest@orionserver.com/msg08677.html If you patch the JDBC driver to read whatever format your dates are coming back as (you should see the actual formatted date string in the exception message), you should be ok. You might first check the CVS copy of the JDBC driver to see if it works; with any luck patches have already been made. Storing dates as strings just seems like a bad idea. It's nice to be able to do date math in SQL queries when you want to analyze your data. Jeff -Original Message- From: Eddie [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:55 AM To: Orion-Interest Subject: bad timestamp confusion Just like other people in the newsgroup, I am receiving a bad timestamp error once in a while with Postgres 7.0. I looked in the newsgroup and saw some possible solutions, but I am a bit confused. How can I solve this problem for ever in case of a DateTime field ??? Someone talked about using java.sql.Date instead of java.util.Date, the other about getting the last postgres jdbc driver I got the last postgres driver from the postgres site, so what should I do ?? I was thinking about just using Strings to store Date format info. What about this ? And what should I do when I get such an error. Filling the database all over again helps. But what, when I have everyting ready online ?? Regards, Eddie
RE: bad timestamp confusion
There are instructions for obtaining the latest source tree via anonymous CVS here: http://www.postgresql.org/devel-corner/docs/postgres/cvs.html Just get the whole thing :-) There are instructions for building the JDBC driver in the README file in the directory you found. Good luck, Jeff -Original Message- From: Eddie [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 1:56 PM To: Orion-Interest Subject: Re: bad timestamp confusion Thanks Jeff, H, I am a bit confused, again. I went searching for the correct postgres jdbc driver, and don't know exactly where to get the last version and source (I thought I did). I seached on http://jdbc.postgresql.org/download/ but is that the correct site ? and where can I get the source as I can't find it. I searched on http://www.postgresql.org/cgi/cvsweb.cgi/pgsql/src/interfaces/j dbc/, but there I only have a complete three and don't realy know what to download. Regards, Ed Bras - Original Message - From: Jeff Schnitzer [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Wednesday, March 21, 2001 8:08 PM Subject: RE: bad timestamp confusion Take a look at this message I posted in January: http://www.mail-archive.com/orion-interest@orionserver.com/msg0 8677.html If you patch the JDBC driver to read whatever format your dates are coming back as (you should see the actual formatted date string in the exception message), you should be ok. You might first check the CVS copy of the JDBC driver to see if it works; with any luck patches have already been made. Storing dates as strings just seems like a bad idea. It's nice to be able to do date math in SQL queries when you want to analyze your data. Jeff -Original Message- From: Eddie [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 21, 2001 4:55 AM To: Orion-Interest Subject: bad timestamp confusion Just like other people in the newsgroup, I am receiving a bad timestamp error once in a while with Postgres 7.0. I looked in the newsgroup and saw some possible solutions, but I am a bit confused. How can I solve this problem for ever in case of a DateTime field ??? Someone talked about using java.sql.Date instead of java.util.Date, the other about getting the last postgres jdbc driver I got the last postgres driver from the postgres site, so what should I do ?? I was thinking about just using Strings to store Date format info. What about this ? And what should I do when I get such an error. Filling the database all over again helps. But what, when I have everyting ready online ?? Regards, Eddie
