Just to drop in a line: We successfully use Interbase 6 as database server
for our entity beans (BMP, so do not ask for a database scheme ;-). It
should fit all the needs the people have that want to use MySQL - first of
all, it's now free... (and, astonishingly, it seems even faster, although i
did no real benchmarking). The JDBC drivers seem stable, but they do not
support long and timestamp values in the database yet (that means, they only
use Interbase dialect 1, not the new one, 3).
Regards
Jens Stutte
> -----Ursprüngliche Nachricht-----
> Von: Richard Woodward [mailto:[EMAIL PROTECTED]]
> Gesendet am: Donnerstag, 17. August 2000 02:30
> An: Orion-Interest
> Cc: Orion-Interest
> Betreff: RE: MySql?
>
> MySQL can be used with EJB's, but entities will have to be
> written in such
> a way as to get around the lack of transaction support, ie.
> using table
> locks (Yuck!). THis however alone does not guarantee data
> integrity, as a
> connection that is dropped in the middle of a set of queries,
> will result
> in the locks being dropped, meaning table locks are only
> useful when two
> concurrect connections are trying to write/ read to the same
> table, and
> locks will ensure that one connection blocks till the other drops the
> lock.
>
> So, you can still do session beans, but not standard entity beans.
>
> MaxSQL is MySQL with Berkeley DB support for transactions.
> THis has been
> announced, but not released yet. I think they are waiting till the
> existing Berkeley DB transactions mod is more stable before
> they release
> it. You could have a preview by getting the Mod and installing it with
> MySQL and seeing how it goes with EJB's under Orion.
>
> Have not had too much of a play with EJB support on Orion yet, but i
> understand you have to create a schema for particular databases to use
> them as EJB datasources ??
>
> cheers,
>
> Richard.
>
> ps. I have been using MySQL for some time on Orion, as a standard
> datasource, but have not tried it with EJB's yet. It is fine
> as a standard
> datasource, the JDBC drivers ( the mm variety ) even have transaction
> handling routines. (commit, rollback, etc... ) They just dont
> work, ie.
> The transaction gets fired through query by query without
> regard for data
> integrity.
>
> ---------------------------
>
> Richard Woodward
>
> G8 Labs Ltd.
>
> Wellington
> New Zealand
>
> Direct Dial (04) 9393414
> ---------------------------
> On Wed, 16 Aug 2000, Michael Bushe wrote:
>
> > Since MySQL doesn't support transactions (hence IMHO is a toy like
> > MSAccess), so I would be surprised if it would work with
> any EJB server. If
> > you want an open source solution I'd try PostgreSQL or
> Inprise's Interbase.
> > I'm starting with Oracle and moving to one of those. I did
> try PostgreSQL
> > with the RI and that worked, so I bet Orion would work too.
> Let us know or
> > I'll let y'all know in a couple of months.
> >
> > Michael
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> Steven Punte
> > Sent: Wednesday, August 16, 2000 1:01 PM
> > To: Orion-Interest
> > Subject: MySql?
> >
> >
> > Has anyone ever use the database "mysql" successfully with Orion?
> >
> > Steve
> >
> >
> > STeve Punte
> > e-Business Software Architect
> > Technologent Inc
> > [EMAIL PROTECTED]
> >
>
>
