install of v5, table types, features

[invinfo]

I don't recall exactly what options I selected in September when I
installed the beta v5.0.4 on my development machine, But, as I started
to develop and then backup data, I noticed that my tables are all using
the storage engine: InnoDB.
Can someone jog my memory and tell me what options cause that to be the
default ?

I'm on the fence, b/w choosing MyISAM and InnoDB
- I don't think I'll be using any transactions or foreign keys, in my
DB/app.
- Re: Performance: With a max of 50 users, I don't think this app will
need stress testing and I don't expect performance to degrade with
either engine.

Since I'm using InnoDB, why is there nothing in the Directory set up
specifically for InnoDB ?
Does that only get used when you start defining foreign keys ?

I'm looking for clarification, advice on a few issues:
Table Locking : the manual's use of the word "thread" made in unclear,
what this does ??
autocommit : ?set to 1 for all non-InnoDB engines ?

Also, whats the best way to convert these tables, if I decide which is
best ?
I notice, that it can be done using, "Alter Table" command.

Suggestions and advice, most welcome. TIA for your replys while I
stew on this.

[invinfo]

anyone have any comments on InnoDB storage or performance ? TIA

[Good Man]

in*****@rcn.com wrote in news:1132353304.978371.81730
@z14g2000cwz.googlegroups.com:

I don't recall exactly what options I selected in September when I
installed the beta v5.0.4 on my development machine, But, as I started
to develop and then backup data, I noticed that my tables are all using
the storage engine: InnoDB.
the 5.0 full release is out... upgrade!
Can someone jog my memory and tell me what options cause that to be the
default ?
all tables are by default created as InnoDB instead of MyISAM in MySQL 5.0
unless specified after installation

I'm on the fence, b/w choosing MyISAM and InnoDB
depends what you're doing.... no transactions (are you really sure? never
more than one table is updated at a time?) then go MyISAM

Since I'm using InnoDB, why is there nothing in the Directory set up
specifically for InnoDB ?
InnoDB stores data completely differently than MyISAM. It's in the
ibdata.0 file or something. No directories are made.

I'm looking for clarification, advice on a few issues:
Table Locking : the manual's use of the word "thread" made in unclear,
what this does ??
table locking prevents alterations to a table while an update is going on
(i think). InnoDB tables can do row-level locking, but MyISAM tables can
only lock the entire table.
autocommit : ?set to 1 for all non-InnoDB engines ?

that means that your 'inserts' and 'updates' happen right away, no
transaction type of action

most of these questions can be answered with a MySQL book or at the very
least some googling