Ok, in today's "the sky is the limit" (in terms of space), do we really
care about 1 or 2 bytes for an integer field type for a primary key?
I'm redesigning FabMate Classic to use a MySQL (MariaDB) database
backend now because my client is still experiencing problems with the
VFP database (index problems, etc.). His network guy (as usual) says
everything on the Windows Server 2016 network is fine and the problems
only started when they upgraded the client workstations from Win7 to
Win10. Whatever. This thread is about primary key size WHEN YOU KNOW
THAT THE MAX VALUE WON'T GO OVER (whatever the limit is at each field
type: 255 for tinyint, etc.)
The OCD part of me wants to define the smallest type possible, whereas
the "let's set it and never worry about it" part of me says "just make
everything INT."
Weigh in on your thoughts on which type you'd use.
tia,
--Mike
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.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.
