Re: Win2k Pro. is messing up the DB
Hello Randahl,
First of all, I appreciate your idea.
Yes, we came to the near conclusion that it was not
orion but it was postgresql.
To tell the truth, I believe in orion but not
very much so in postgresql.
As a matter of fact, we are using a CVS version of
PostgreSQL because
the released version of postgresql does not yet
support the right join sql statement.
To make matters worse, the Linux JDBC driver was
not working properly on the timestamp
field before I made a modification on the driver.
We were totally forgetting all about this.
Our Windows developers have had no problems
with ODBC drivers so far, out of which
we can guess it is not the DB itself but it is the
Linux JDBC driver.
What are your thoughts?
Once again, thank you very much.
Simon
- Original Message -
From:
Randahl Fink
Isaksen
To: Orion-Interest
Sent: Friday, February 23, 2001 1:07
AM
Subject: RE: Win2k Pro. is messing up the
DB
I
know this is a wild guess, but just to make sure, I would of course do a disk
scan on that machine to make sure it is not a hardware problem - these things
do happen, I am afraid.
Another good thing would be to run the application on
a _different_ Win2K Pro. machine to make sure it is not just something which
is specific to only her single machine.
BTW,
I would doubt PostgreSQL more on Win2K than I would doubt Orion. Orion is a
java application, which gives it a pretty good chance of running in the same
way on different platforms. To the best of my knowledge PostgreSQL on Win2K is
a port of the code from another platform, and from reading articles at
PostgreSQL's web-site it seems it is not totally stable on Win2K. I have seen
at least two posts on this list where people recommends *not* using PostgreSQL
from Win NT based systems - not yet, anyway.
I
have used Orion on Win2K with no problems - but then again I do *not* use
PostgreSQL
Hope
you find a solution
Yours
Randahl
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]Sent: 23. februar 2001 02:19To:
Orion-InterestSubject: Win2k Pro. is messing up the
DB
Hello,
I do not really know if this is because she's
using Window 2000 Professional.
All our employees use Windows 2000 Servers or
Linuxes or Solarises except for one person.
The exception is Windows 2000 Professional. The
problem occurs only at her computer.
Once she updates a DB record, it messes up
another record. This does not
happen all the time, but once in a blue moon.
This is why I can't catch the problem in my code.
And I do not think it is my code. I
am using CMPs and orion 1.3.8 with PostgreSQL.
I doubted postgresql and orion in the
beginning, and now I narrowed it down to orion because
it may be machine specific as I mentioned
earlier. Why does a DB server have to do with
a specific machine? Then what? An App. Server
which holds a session to a machine?
I am lost. Does anyone have any clue? I really
really hope it's my code.
I appreciate your attention.
Simon
RE: Win2k Pro. is messing up the DB
I know this is a wild guess, but just to make sure, I would of course do a disk scan on that machine to make sure it is not a hardware problem - these things do happen, I am afraid. Another good thing would be to run the application on a _different_ Win2K Pro. machine to make sure it is not just something which is specific to only her single machine. BTW, I would doubt PostgreSQL more on Win2K than I would doubt Orion. Orion is a java application, which gives it a pretty good chance of running in the same way on different platforms. To the best of my knowledge PostgreSQL on Win2K is a port of the code from another platform, and from reading articles at PostgreSQL's web-site it seems it is not totally stable on Win2K. I have seen at least two posts on this list where people recommends *not* using PostgreSQL from Win NT based systems - not yet, anyway. I have used Orion on Win2K with no problems - but then again I do *not* use PostgreSQL Hope you find a solution Yours Randahl -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED]Sent: 23. februar 2001 02:19To: Orion-InterestSubject: Win2k Pro. is messing up the DB Hello, I do not really know if this is because she's using Window 2000 Professional. All our employees use Windows 2000 Servers or Linuxes or Solarises except for one person. The exception is Windows 2000 Professional. The problem occurs only at her computer. Once she updates a DB record, it messes up another record. This does not happen all the time, but once in a blue moon. This is why I can't catch the problem in my code. And I do not think it is my code. I am using CMPs and orion 1.3.8 with PostgreSQL. I doubted postgresql and orion in the beginning, and now I narrowed it down to orion because it may be machine specific as I mentioned earlier. Why does a DB server have to do with a specific machine? Then what? An App. Server which holds a session to a machine? I am lost. Does anyone have any clue? I really really hope it's my code. I appreciate your attention. Simon
Win2k Pro. is messing up the DB
Hello, I do not really know if this is because she's using Window 2000 Professional. All our employees use Windows 2000 Servers or Linuxes or Solarises except for one person. The exception is Windows 2000 Professional. The problem occurs only at her computer. Once she updates a DB record, it messes up another record. This does not happen all the time, but once in a blue moon. This is why I can't catch the problem in my code. And I do not think it is my code. I am using CMPs and orion 1.3.8 with PostgreSQL. I doubted postgresql and orion in the beginning, and now I narrowed it down to orion because it may be machine specific as I mentioned earlier. Why does a DB server have to do with a specific machine? Then what? An App. Server which holds a session to a machine? I am lost. Does anyone have any clue? I really really hope it's my code. I appreciate your attention. Simon
