Hi Mike > Message: 2 > Date: Tue, 23 Jan 2007 16:26:47 -0500 > From: MB Software Solutions <[EMAIL PROTECTED]> > Subject: Numeric(3) versus Integer field in VFP8/9 database table > To: [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="us-ascii" > > I need to add a column for "release #" in one of my tables. A > numeric(3) would be plenty, but I wonder if I shouldn't just make it an > integer and be done with it. I don't expect the field to be indexed, so > I guess this is just silliness over 1 byte, eh? > > Can anyone name a valid reason why you'd make it INTEGER type instead of > NUMERIC(3)?
IIRC numeric is a character field converted to a numeric value and back regulary. Integer stays integer throughout. So I'd guess integer will be faster. Besides you KNOW the user will want 4 digits next week. :) Mike _______________________________________________ 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 ** 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.
