• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Anyone using InnoDB table type with MySQL/WebObjects?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Anyone using InnoDB table type with MySQL/WebObjects?


  • Subject: Re: Anyone using InnoDB table type with MySQL/WebObjects?
  • From: Kieran Kelleher <email@hidden>
  • Date: Tue, 22 Jun 2004 16:57:09 -0400

Jean Pierre,

I just did a test and converted all tables in a WO project to InnoDB. I then turned on EODebuggingEnabled on the Wo app server so I could see the SQL

I deliberately logged from different computers into two separate instances of the WO app and opened and changed the same record and a related one-to-many record was added to the changed record. When I saved in both apps, the second one threw, as expected, an optimistic locking exception. I checked the eof log and found no COMMIT/ROLLBACK SQL, however when I checked the database itself, I found that MySQL did indeed roll back the transaction, so the EOF "Internal Begin", "Internal Commit" and "Internal Rollback" do seem to corespond to SQL BEGIN/ROLLBACK and COMMIT .... but you will not see it in the standard EOF debug logging output.

... and THAT is GREAT news ...... open source MySQL InnoDB engine that has ACID transactional capability that works with WO.

FYI, on Jeremy Zawdowny's new book "High Performance MySQL" in Chapter 2, he explains how the different available storage engines in MySQL work and one point of interest (page 20) is that MySQL InnoDB uses Multi-Version Concurrency Control just like Oracle and PostgreSQL.

This is a great book. I just set up master-slave replication in minutes using the instructions in the book and now can keep the master dbs up 24/7 and backup the slave

http://www.amazon.com:80/exec/obidos/ASIN/0596003064/kieranwebobje-20? creative=125581&camp=2321&link_code=as1

-Kieran

________________________________________________________________
Config = OS X 10.3.4 / Java 1.4.2 / WO 5.2.3 / XCode v1.2 / MySQL 4.0.20 / Connector-J 3.0.11
Blog: http://webobjects.webhop.org/



On Jun 17, 2004, at 3:09 AM, Jean Pierre Malrieu wrote:



Up to now I have used the MyISAM default table (db engine) type with
WebObjects. Is anyone usingMySQL InnoDB tables with WebObjects? If so,
how do you take advantage of transaction begin/commit/rollback features
of such a transaction-safe ddatabase ...... or is db transaction
handling built-in to the specific database JDBC driver in which case I
doubt the MySQL driver begins/commits/rollsback since I have never seen
SQL statements for transactions being generated for editing context
saves??


-Kieran

I do use EOF with MySQL/InnoDB. It works.
I remember I attended a presentation by Frank Sylvestre on this topic. He showed us that EOF generated begin, and commit statements, and that MySQL with InnoDB rolledback as expected when a problem was raised.


In addition, modifying the table type is as easy as sending a Alter Table command, and InnoDB tables can be backed up with mysqldump.

Isn't that great?

JP.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: Anyone using InnoDB table type with MySQL/WebObjects?
      • From: Chuck Hill <email@hidden>
References: 
 >Re: Anyone using InnoDB table type with MySQL/WebObjects? (From: Jean Pierre Malrieu <email@hidden>)

  • Prev by Date: Re: Duplicate records
  • Next by Date: Re: Anyone using InnoDB table type with MySQL/WebObjects?
  • Previous by thread: Re: Anyone using InnoDB table type with MySQL/WebObjects?
  • Next by thread: Re: Anyone using InnoDB table type with MySQL/WebObjects?
  • Index(es):
    • Date
    • Thread