Tuesday, August 30, 2005

The little things that snowball

There's nothing more I can say about this.
CREATE TABLE INVOICE_LINEITEM 
(
...
...
MONTH_OF_YEAR   CHAR(1)
...
)

8 comments:

William Robertson said...

Come on, it's August and the app's still working just fine. What could possibly go wrong?

Robert Vollman said...

Well, it is a CHAR. So technically they can have some kind of mapping...

Or maybe its a Boolean. As in 'Y', it is a month of the year, or 'N' - there is no 'March' this year.

:)

Michael Dinh said...
This comment has been removed by a blog administrator.
Michael Dinh said...

What if the person was trying to save space?

What if the person was using hexadecimal for month?

I have to admit; I have never executed such a design in the database.

However, I have used the convention for labeling tape sent to offsite storage.

For example: 5A22prod – August 22, 2005.

DaPi said...

Y2K - nothing!

I worked on an accounting system with a single digit for the year.

Thai Rices said...


"Well, it is a CHAR. So technically they can have some kind of mapping..."


This is why this posting is called "The Little Things That Snowball"

OraWTFGuy said...

So does J map to January, June or July? Actually, that's a foolish question, because *obviously* J will map to October. Huh?

Yanivus said...

If the app work for "M"ay, it works!!! woohoo!