Randy: Tuesday, October 7, 2003, 4:49:44 PM, você escreveu:
---------------[inicio]------------------ RC> Apologies for the length of this post. RC> We started off this little proof of concept project using MySQL RC> InnoDB RC> tables, in part because we figured we needed foreign key constraints, RC> row locking, and all the other bells and whistles that one gets with RC> DB2 (our production DB on a big - for us - project). RC> We are creating a reports-only application for billing and accounts RC> receivable information now kept in a Lotus Notes database. We will RC> export the billing information every night and do a load into MySQL. RC> We will then use Crystal Reports (and perhaps later a Java GUI) to RC> generate various reports like aged accounts, cash receipts, this by RC> office, that by month, etc. etc. While good RDBMS design says we RC> should have half a dozen tables all glued together with foreign key RC> constraints, I'm not sure any of that really applies. It's not a RC> transactional database, reads and writes will essentially never be RC> concurrent so row locking is not an issue, and logging in this RC> environment doesn't seem productive. On the other hand, we have a RC> moderately strong dedicated server with 1 GB ram and 150 GB drive RC> space, so resources to run one table type over another also don't RC> seem RC> relevent. On the gripping hand, the collective experience around here RC> is with DB2, so on some level, some of us expect to find things like RC> transaction logs, commit and rollback capability, and such like even RC> if we never have occasion to use them. RC> So, how's a person to decide? To MyIsam or not to MyIsam, that is the RC> question. RC> Thanks and apologies again for the long post. RC> Randy RC> -- RC> MySQL General Mailing List RC> For list archives: http://lists.mysql.com/mysql RC> To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] ---------------[cortar]------------------ it always uses InnoDB. My company used MyISAM for many data... had problems with competing access. With innodb we did not have plus no claim. For great volume of data, InnoDB. InnoDB,Query,MySQL ------------------------------------------------------------------------- ++ Dyego Souza do Carmo ++ Dep. Desenvolvimento ------------------------------------------------------------------------- E S C R I B A I N F O R M A T I C A ------------------------------------------------------------------------- The only stupid question is the unasked one (somewhere in Linux's HowTo) Linux registred user : #230601 -- ICQ : 1647350 $ look into "my eyes" Phone : +55 041 2106-1212 look: cannot open my eyes Fax : +55 041 296 -6640 ------------------------------------------------------------------------- Reply: [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
