﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Joe Celko  / Stairway to Data, Step 8: Data Encoding Schemes - Part II / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Tue, 21 May 2013 23:14:54 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Stairway to Data, Step 8: Data Encoding Schemes - Part II</title><link>http://www.sqlservercentral.com/Forums/Topic1107652-1604-1.aspx</link><description>Nice series!With this:[quote]The translation tables can be downloaded to the workstations in a client/server system to reduce network traffic. [/quote]I do have the opposite experience. I have to work with a system which sends data over the internet and has a Java front end on the client PC. That front end downloads ALL these code tables and does it every time something was changed. And there are often changes. It does it no matter if I need the translation data or not, so the traffic finally increased. I would prefer a picker form which the user calls when necessary and which queries just the codes which are needed.</description><pubDate>Fri, 18 Nov 2011 12:48:52 GMT</pubDate><dc:creator>Philipp Post</dc:creator></item><item><title>RE: Stairway to Data, Step 8: Data Encoding Schemes - Part II</title><link>http://www.sqlservercentral.com/Forums/Topic1107652-1604-1.aspx</link><description>Nines and zeroes go back to punch cards!FORTRAN and early COBOL progam read a blank (unpunched) card column as a zero. You could go back and re-punch the card when you knew something. The columns were locked to alpha, numeric or alphanumeric by the keypunch (there was a control card that shifted the keyboard for you). The keys also did repetition if you held them down. That mean that filling a card field with nines would make them sort to the end of the deck and the bottom of reports. This is also why we has a lot of people born in '1911-11-11'  when we did not know the real birthdate (remember 2-digit years and "mmddyy" dates in COBOL). </description><pubDate>Wed, 31 Aug 2011 08:15:42 GMT</pubDate><dc:creator>CELKO</dc:creator></item><item><title>RE: Stairway to Data, Step 8: Data Encoding Schemes - Part II</title><link>http://www.sqlservercentral.com/Forums/Topic1107652-1604-1.aspx</link><description>Joe, any history on why they used "9" for the no gender value instead of "3", the next in the sequence?</description><pubDate>Wed, 31 Aug 2011 05:35:41 GMT</pubDate><dc:creator>Andy Warren</dc:creator></item><item><title>Stairway to Data, Step 8: Data Encoding Schemes - Part II</title><link>http://www.sqlservercentral.com/Forums/Topic1107652-1604-1.aspx</link><description>Comments posted to this topic are about the item [B]&lt;A HREF="/articles/Stairway+Series/Designing+encoding+schemes/72664/"&gt;Stairway to Data, Step 8: Data Encoding Schemes - Part II&lt;/A&gt;[/B]</description><pubDate>Thu, 12 May 2011 06:53:04 GMT</pubDate><dc:creator>CELKO</dc:creator></item></channel></rss>