It
could be that Interbase is a very recent addition to the open source / freeware
bunch. Also, prior to version 6, Interbase was
missing some essential data types, which made it a bit
less approchable. My company is still evaluating Interbase, but so
far
we
haven't found any "issues" and are extremely pleased with the JDBC driver and
the performance/features of this product.
There
appears to be an issue setting different character sets for the JDBC driver in
data-sources.xml, but that is probably true
for
all JDBC drivers and setting their extended parameters (it could be a problem
with Orion) and it's not a show stopper for us.
At
some point in time, we were also evaluating mySQL, but (AT THE TIME) it had no
transaction support, JDBC drivers were
in
flux and no blobs.
Personally, I believe that InterBase 6 offers more
features then mySQL. Another FREE option appears to come from
SAP
driver
and a bunch of tools. It would be nice to hear from somebody who know more about
it.
-arno
You
are probably right in your asumptions. Might I ask why you have chosen to go
for PostgreSQL? To me it seems a bit too uncertain to have two pieces of
experimental software in one project. Personally I was thinking of switching
to either MySQL or Interbase once my system goes on-line. I have used
Interbase quite a lot, just not with EJBs, and it is totally free and open
source nowadays. I have no experience with MySQL, but as far as I have read on
this list, quite many people are fond of it, and it seems that the use of
MySQL is a question of once needs for transactions (which MySQL does not
support).
I am
wondering if anyone is using the prepackaged Hypersonic database in
production... It has not given me any trouble during this development
project... yet... - I would feel MUCH better about using a 10+ years old
well-tested database like Interbase, and I simply do not know why more people
are not using it.
Any
comments anyone?
Randahl
-----Original Message----- From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED] Sent: 23. februar 2001 18:39 To:
Orion-Interest Subject: 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 -----
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
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
|