Posted by Peter Fox on 06/07/05 08:31

Following on from 's message. . .
>I have been using flat files for a while but thought I should learn
>mysql. There are two things I dont like about mysql compared to using
>flatfiles. They are:
* Go with MySQL (almost) every time
* The documentation is clear and extensive
* Installation and integration is a doddle
* myadmin takes the hassle out of learning all the DDL stuff
* You are bound to need database features sooner rather than later so
bite the bullet - the learning curve is not difficult.
* Your questions will soon be answered when you get more familiar
* Flat files have lots of overheads - both computationally and hassle of
use. (Even a log file such as an audit trail, if it is to be analysed,
is probably better as a table.) - Don't even mention multi-user
aspects.






>
>1) When creating a table why do I need to define the type of data and
>length so strictly, i,e int , varchar etc? Can I make a flexible table
>with data of any type and length?
>
>2) When creating a record I am using autoincrement ID. This works
>great except when I delete a record it leaves a "hole" in the table.
>How can I set it up to work like a flatfile where all records shift
>"up" when one is deleted?
>
>Any good tutorials that cover this?
>
>Thanks,
>

--
PETER FOX Not the same since the poster business went to the wall
peterfox@eminent.demon.co.uk.not.this.bit.no.html
2 Tees Close, Witham, Essex.
Gravity beer in Essex <http://www.eminent.demon.co.uk>

[Back to original message]