× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Joe,

This is an implementation detail that used to be important (visible and with a shared best way) but now it isn't. You might need packed or binary for performance, zoned for readability of the raw data or floating-point because it matches a related database. From the other answers here we are moving away from working directly with the raw data. IMHO it's less about using the 'best' format than having a flexible database that can change to the most appropriate format without breaking code. That's why using embedded SQL instead of directly accessing the data with RPG is a good idea. SQL won't break (or it will break less) if you change the numeric format but RPG will break (maybe or probably and it requires a recompile). That's also why using a database retrieval tool (Query, DBU, SQL) instead of viewing the raw data is also good. Hiding details that aren't important makes it easy.

Paul Morgan

Principal Programmer Analyst
IT Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Friday, September 02, 2011 8:02 AM
To: Midrange Systems Technical Discussion
Subject: Storing Numeric Values in the Database

Generally speaking, what is the current wisdom about storing numeric
data in the database? Do folks still prefer packed representation for
data with decimal positions? Zoned is a little easier on the eyes when
looking at a raw record, but it takes a few more bytes especially as the
fields get larger. And as far as I know RPG still likes to convert
things to packed when it reads a file unless you tell it not to. That
being the case is there still a performance issue these days?

We like zoned fields here, but I'm trying to address the issue from a
thorough technical standpoint. If you're trying to be as lean as
possible, you could argue that integers should be stored in binary,
although that has its own issues. Heck, an argument could be made that
you should store all data as integers with implied digits and decimal
positions.

What say you all?

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.