大阪のアプリ開発会社 ギガスジャパン

ホーム
アプリ関連ニュース

アプリ関連ニュース

2020年9月18日
VR

Facebook「Oculus Quest 2」を発表

2020年9月16日に開催されたFacebook Connect 7で、新型VRヘッドセット「Oculus Quest 2」が発表されました。これは現行製品の「Oculus Quest」の後継となるPC不要のスタンドアロン一体型VRヘッドセットです。

nishida at 2020年09月18日 10:00:14

2020年9月16日
他の話題

今週発売予定の新世代GPUについて

今週はRTX3080の発売が予定されていますね。
これがどのようなものか少し調べてみました。

tanaka at 2020年09月16日 10:00:22

2020年9月11日
技術情報

InnoDB vs MyISAM

I talked about what is the MySQL storage engine last week. Today I will talk about the main difference between InnoDB and MyISAM.

The main difference between MyISAM and InnoDB are :

MyISAM does not support transactions by tables while InnoDB supports.

There are no possibility of row-level locking, relational integrity in MyISAM but with InnoDB this is possible. MyISAM has table-level locking.

InnoDB does not support FULLTEXT index while MyISAM supports.

Performance speed of MyISAM table is much higher as compared with tables in InnoDB.

InnoDB is better option while you are dealing with larger database because it supports transactions, volume while MyISAM is suitable for small project.

As InnoDB supports row-level locking which means inserting and updating is much faster as compared with MyISAM.

InnoDB supports ACID (Atomicity, Consistency, Isolation and Durability) property while MyISAM does not support.

In InnoDB table,AUTO_INCREMENT field is a part of index.

Once table in InnoDB is deleted then it can not re-establish.

InnoDB does not save data as table level so while implementation of select count(*) from table will again scan the whole table to calculate the number of rows while MyISAM save data as table level so you can easily read out the saved row number.

MyISAM does not support FOREIGN-KEY referential-integrity constraints while InnoDB supports.

By Yuuma

yuuma at 2020年09月11日 11:00:28