Yes, in this case INT is much better because it only need 4 bytes on disk and have direct hex interpretation, while the number occupies 10 bytes and need digit by digit calculation.
Being both data types related, I thing that it's a secure assumption that the number field can be replaced by the INT data type. El jue., 5 de abril de 2018 5:05, < mbsoftwaresoluti...@mbsoftwaresolutions.com> escribió: > On 2018-04-04 16:53, Fernando D. Bozzo wrote: > > Not counting legacy reasons for already available systems, I think that > > this is because many did not learn about the available data types and > > just > > stay with what they know, others because did think that are the same, > > and > > others because they don't care. > > > > I know some of those guys, btw. > > > ALBEIT PROBABLY MINISCULE, won't the Integer type be a better, more > efficient, faster processing choice? I noticed in this app I inherited, > the main table where it's the PK, it's an INTEGER type, but in a another > table where it's the foreign key, it's a N(10,0) type. I'll have to > break out SYS(3054) I guess to see if it optimizes, given the > difference! > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com 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/CAGQ_JukqbCLryDREi_8HvtF=vOjSdX_EU3gRUm6C1hDa4c=x...@mail.gmail.com ** 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.
