Link Details

Link 453915 thumbnail
User 225256 avatar

By mswatcher
via marksverbiage.blogspot.com
Published: Jul 24 2010 / 12:05

Here are a lot of weird things which MySQL does to handle its mix of transactional and non-transactional behaviour, but this one was new to me
  • 25
  • 1
  • 4208
  • 5

Comments

Add your comment
User 254233 avatar

alien3d replied ago:

-4 votes [show comment] Vote down Vote up Reply
User 254233 avatar

alien3d replied ago:

-1 votes Vote down Vote up Reply

Maybe i need to collabrate futher for the negative voter.
For logging purpose.
1.Mysql myisam don't have transaction.
2.Innodb have transaction
3.In my code,all sql will be logged to the myisam table.The reason was myisam don't have transaction.If i put in innodb table.It wouldn't put in the table.
For reporting purpose
1.Myisam much faster on data mining.

Conclusion
Used the right tools for the right development. It's basic rule for programmer.

User 782761 avatar

secci replied ago:

1 votes Vote down Vote up Reply

i just love the title... i've thought that a few times myself.

User 755449 avatar

aionescu replied ago:

5 votes Vote down Vote up Reply

> MySQL, what are you smoking?
Some SQL join(t)?

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Apache Hadoop
Written by: Piotr Krewski
Featured Refcardz: Top Refcardz:
  1. Play
  2. Akka
  3. Design Patterns
  4. OO JS
  5. Cont. Delivery
  1. Play
  2. Java Performance
  3. Akka
  4. REST
  5. Java