On Nov 4, 2007, at 8:05 AM, MB Software Solutions wrote:
> I'm building an app that will utilize a MySQL5 database over the web
> using a VFP9 client. I've read the MySQL book about FIXED rows being
> quicker (just as we know in VFP) for MyISAM tables but the cost is
> space. The alternative is to use a DYNAMIC row format, which won't
> waste space, but the con of that is that searches may take longer and
> there's more chance for fragmentation over time.
Unless database search speed is the bottleneck of your project, I
wouldn't focus on this, and just use the database indexes carefully
to optimize searches. If it turns out later on that search and
retrieval is unacceptably slow, you can always convert from varchar/
text fields to char fields and see if that helps.
One thing to keep in mind is that MySQL doesn't use indexes as VFP
does. It can only use one index per query, so if you have a search on
two columns and an index on each column, it will only optimize one of
the column searches. This article explains things very well:
http://www.myelin.co.nz/post/2005/2/10/#200502102
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
