||Thanks Aaron for pointing this out.
|I still do nut fully understand the implications of not having any
|transactions on the database level. As long as just one application
Actually the decision to commit the data is done at teh app layer by the app
server with or without enrolment of the connection in the transaction. So
yes the "not having the db" participating is not a 'show stopper', just that
if the db goes down during a write you are screwed.
|server uses the database I can't see how data could get corrupted. I
|thought the application server guarantees to have synchonized business
|method calls. And after each call the data is stored back into the
|database. Where does the corruption come in ?
No corruption I agree. The corruption is only if the "write" goes bad, but
the application Tx is only in EJB layer.
|Will transactions allow me to run two or more application servers with
|just one _shared_ database ?
Actually yes
marc
|Aaron Mulder wrote:
|>
|> Please note that you must use extreme caution with mySQL: it did
|> not support transactions until very recently (v 3.23.6?), and
|even now you
|> must install an add-on product and specifically indicate that
|*each table*
|> should be transaction-safe when you create it. Since the default table
|> type is not transaction-safe, *you cannot allow JAWS to create tables for
|> you*, and that means this mapping is not very useful.
|> Because nearly all MySQL installations are not set up for
|> transactions, and J2EE depends on databases supporting transactions, we
|> strongly recommend that you consider another product (such as
|> PostgreSQL). If you are absolutely sure that everything is set up
|> correctly for transactions, and you manually create all tables that your
|> EJBs will use, then it should work, but again I would recommend
|mySQL only
|> as a last resort - if you make any mistakes in the configuration, you are
|> setting yourself up for data corruption.
|>
|> Aaron
|>
|> On Wed, 8 Nov 2000, Tobias Frech wrote:
|> > Hi mySQL users!
|> > As my new and tested mySQL type-mapping didn't make it into
|the new beta
|> > (Sebastien, how are you?) I'd like to post it here to make the live
|> > easier for all you guys who want to use mySQL. Tested with
|> > dbtest/AllTypes package.
|> >
|> > for [standard]jaws.xml:
|<mapping deleted. look in older mails>
|> > You'll find additional docu under bug #219 and #220
|> > (http://www.telkel.com/bugzilla/).
|> >
|> > Have phun.
|> >
|> > Tobias
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
