Hi,
(better change the message subject if you change, well, the subject)
> user will create more number of tickets per day. so INSERT, UPDATE, SELECT
> will use highly.
>
> in document says' Myisam will not support transaction but it has self
> backup
> and restoration method. but in InnoDB good for transaction but no self
> managed backup and restoration..
>
> now how can i choose my engine. ?
>
> my usage is only storage and retrieve data.. so which one is normally
> preferred by all developers
Quite simple really: do you need to store data in one table that depends
on other data in other tables?
If the answer is YES, then use transactions. Without transactions, you
cannot guarantee the data consistency.
With regards,
Martijn Tonies
Upscene Productions
http://www.upscene.com
Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!
Database questions? Check the forum:
http://www.databasedevelopmentforum.com

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.