Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Stupidest table I ever saw

27 views
Skip to first unread message

Mikito Harakiri

unread,
May 17, 2001, 5:48:09 PM5/17/01
to
Name Null? Type
------------------------------- -------- ----
PRICING_ATTRIBUTE1 VARCHAR2(240)
PRICING_ATTRIBUTE2 VARCHAR2(240)
PRICING_ATTRIBUTE3 VARCHAR2(240)
PRICING_ATTRIBUTE4 VARCHAR2(240)
PRICING_ATTRIBUTE5 VARCHAR2(240)
PRICING_ATTRIBUTE6 VARCHAR2(240)
PRICING_ATTRIBUTE7 VARCHAR2(240)
PRICING_ATTRIBUTE8 VARCHAR2(240)
PRICING_ATTRIBUTE9 VARCHAR2(240)
PRICING_ATTRIBUTE10 VARCHAR2(240)
PRICING_ATTRIBUTE11 VARCHAR2(240)
PRICING_ATTRIBUTE12 VARCHAR2(240)
PRICING_ATTRIBUTE13 VARCHAR2(240)
PRICING_ATTRIBUTE14 VARCHAR2(240)
PRICING_ATTRIBUTE15 VARCHAR2(240)
PRICING_ATTRIBUTE16 VARCHAR2(240)
PRICING_ATTRIBUTE17 VARCHAR2(240)
PRICING_ATTRIBUTE18 VARCHAR2(240)
PRICING_ATTRIBUTE19 VARCHAR2(240)
PRICING_ATTRIBUTE20 VARCHAR2(240)
PRICING_ATTRIBUTE21 VARCHAR2(240)
PRICING_ATTRIBUTE22 VARCHAR2(240)
PRICING_ATTRIBUTE23 VARCHAR2(240)
PRICING_ATTRIBUTE24 VARCHAR2(240)
PRICING_ATTRIBUTE25 VARCHAR2(240)
PRICING_ATTRIBUTE26 VARCHAR2(240)
PRICING_ATTRIBUTE27 VARCHAR2(240)
PRICING_ATTRIBUTE28 VARCHAR2(240)
PRICING_ATTRIBUTE29 VARCHAR2(240)
PRICING_ATTRIBUTE30 VARCHAR2(240)
PRICING_ATTRIBUTE31 VARCHAR2(240)
PRICING_ATTRIBUTE32 VARCHAR2(240)
PRICING_ATTRIBUTE33 VARCHAR2(240)
PRICING_ATTRIBUTE34 VARCHAR2(240)
PRICING_ATTRIBUTE35 VARCHAR2(240)
PRICING_ATTRIBUTE36 VARCHAR2(240)
PRICING_ATTRIBUTE37 VARCHAR2(240)
PRICING_ATTRIBUTE38 VARCHAR2(240)
PRICING_ATTRIBUTE39 VARCHAR2(240)
PRICING_ATTRIBUTE40 VARCHAR2(240)
PRICING_ATTRIBUTE41 VARCHAR2(240)
PRICING_ATTRIBUTE42 VARCHAR2(240)
PRICING_ATTRIBUTE43 VARCHAR2(240)
PRICING_ATTRIBUTE44 VARCHAR2(240)
PRICING_ATTRIBUTE45 VARCHAR2(240)
PRICING_ATTRIBUTE46 VARCHAR2(240)
PRICING_ATTRIBUTE47 VARCHAR2(240)
PRICING_ATTRIBUTE48 VARCHAR2(240)
PRICING_ATTRIBUTE49 VARCHAR2(240)
PRICING_ATTRIBUTE50 VARCHAR2(240)
PRICING_ATTRIBUTE51 VARCHAR2(240)
PRICING_ATTRIBUTE52 VARCHAR2(240)
PRICING_ATTRIBUTE53 VARCHAR2(240)
PRICING_ATTRIBUTE54 VARCHAR2(240)
PRICING_ATTRIBUTE55 VARCHAR2(240)
PRICING_ATTRIBUTE56 VARCHAR2(240)
PRICING_ATTRIBUTE57 VARCHAR2(240)
PRICING_ATTRIBUTE58 VARCHAR2(240)
PRICING_ATTRIBUTE59 VARCHAR2(240)
PRICING_ATTRIBUTE60 VARCHAR2(240)
PRICING_ATTRIBUTE61 VARCHAR2(240)
PRICING_ATTRIBUTE62 VARCHAR2(240)
PRICING_ATTRIBUTE63 VARCHAR2(240)
PRICING_ATTRIBUTE64 VARCHAR2(240)
PRICING_ATTRIBUTE65 VARCHAR2(240)
PRICING_ATTRIBUTE66 VARCHAR2(240)
PRICING_ATTRIBUTE67 VARCHAR2(240)
PRICING_ATTRIBUTE68 VARCHAR2(240)
PRICING_ATTRIBUTE69 VARCHAR2(240)
PRICING_ATTRIBUTE70 VARCHAR2(240)
PRICING_ATTRIBUTE71 VARCHAR2(240)
PRICING_ATTRIBUTE72 VARCHAR2(240)
PRICING_ATTRIBUTE73 VARCHAR2(240)
PRICING_ATTRIBUTE74 VARCHAR2(240)
PRICING_ATTRIBUTE75 VARCHAR2(240)
PRICING_ATTRIBUTE76 VARCHAR2(240)
PRICING_ATTRIBUTE77 VARCHAR2(240)
PRICING_ATTRIBUTE78 VARCHAR2(240)
PRICING_ATTRIBUTE79 VARCHAR2(240)
PRICING_ATTRIBUTE80 VARCHAR2(240)
PRICING_ATTRIBUTE81 VARCHAR2(240)
PRICING_ATTRIBUTE82 VARCHAR2(240)
PRICING_ATTRIBUTE83 VARCHAR2(240)
PRICING_ATTRIBUTE84 VARCHAR2(240)
PRICING_ATTRIBUTE85 VARCHAR2(240)
PRICING_ATTRIBUTE86 VARCHAR2(240)
PRICING_ATTRIBUTE87 VARCHAR2(240)
PRICING_ATTRIBUTE88 VARCHAR2(240)
PRICING_ATTRIBUTE89 VARCHAR2(240)
PRICING_ATTRIBUTE90 VARCHAR2(240)
PRICING_ATTRIBUTE91 VARCHAR2(240)
PRICING_ATTRIBUTE92 VARCHAR2(240)
PRICING_ATTRIBUTE93 VARCHAR2(240)
PRICING_ATTRIBUTE94 VARCHAR2(240)
PRICING_ATTRIBUTE95 VARCHAR2(240)
PRICING_ATTRIBUTE96 VARCHAR2(240)
PRICING_ATTRIBUTE97 VARCHAR2(240)
PRICING_ATTRIBUTE98 VARCHAR2(240)
PRICING_ATTRIBUTE99 VARCHAR2(240)
PRICING_ATTRIBUTE100 VARCHAR2(240)
PRICING_CONTEXT VARCHAR2(30)
QUALIFIER_ATTRIBUTE1 VARCHAR2(240)
QUALIFIER_ATTRIBUTE2 VARCHAR2(240)
QUALIFIER_ATTRIBUTE3 VARCHAR2(240)
QUALIFIER_ATTRIBUTE4 VARCHAR2(240)
QUALIFIER_ATTRIBUTE5 VARCHAR2(240)
QUALIFIER_ATTRIBUTE6 VARCHAR2(240)
QUALIFIER_ATTRIBUTE7 VARCHAR2(240)
QUALIFIER_ATTRIBUTE8 VARCHAR2(240)
QUALIFIER_ATTRIBUTE9 VARCHAR2(240)
QUALIFIER_ATTRIBUTE10 VARCHAR2(240)
QUALIFIER_ATTRIBUTE11 VARCHAR2(240)
QUALIFIER_ATTRIBUTE12 VARCHAR2(240)
QUALIFIER_ATTRIBUTE13 VARCHAR2(240)
QUALIFIER_ATTRIBUTE14 VARCHAR2(240)
QUALIFIER_ATTRIBUTE15 VARCHAR2(240)
QUALIFIER_ATTRIBUTE16 VARCHAR2(240)
QUALIFIER_ATTRIBUTE17 VARCHAR2(240)
QUALIFIER_ATTRIBUTE18 VARCHAR2(240)
QUALIFIER_ATTRIBUTE19 VARCHAR2(240)
QUALIFIER_ATTRIBUTE20 VARCHAR2(240)
QUALIFIER_ATTRIBUTE21 VARCHAR2(240)
QUALIFIER_ATTRIBUTE22 VARCHAR2(240)
QUALIFIER_ATTRIBUTE23 VARCHAR2(240)
QUALIFIER_ATTRIBUTE24 VARCHAR2(240)
QUALIFIER_ATTRIBUTE25 VARCHAR2(240)
QUALIFIER_ATTRIBUTE26 VARCHAR2(240)
QUALIFIER_ATTRIBUTE27 VARCHAR2(240)
QUALIFIER_ATTRIBUTE28 VARCHAR2(240)
QUALIFIER_ATTRIBUTE29 VARCHAR2(240)
QUALIFIER_ATTRIBUTE30 VARCHAR2(240)
QUALIFIER_ATTRIBUTE31 VARCHAR2(240)
QUALIFIER_ATTRIBUTE32 VARCHAR2(240)
QUALIFIER_ATTRIBUTE33 VARCHAR2(240)
QUALIFIER_ATTRIBUTE34 VARCHAR2(240)
QUALIFIER_ATTRIBUTE35 VARCHAR2(240)
QUALIFIER_ATTRIBUTE36 VARCHAR2(240)
QUALIFIER_ATTRIBUTE37 VARCHAR2(240)
QUALIFIER_ATTRIBUTE38 VARCHAR2(240)
QUALIFIER_ATTRIBUTE39 VARCHAR2(240)
QUALIFIER_ATTRIBUTE40 VARCHAR2(240)
QUALIFIER_ATTRIBUTE41 VARCHAR2(240)
QUALIFIER_ATTRIBUTE42 VARCHAR2(240)
QUALIFIER_ATTRIBUTE43 VARCHAR2(240)
QUALIFIER_ATTRIBUTE44 VARCHAR2(240)
QUALIFIER_ATTRIBUTE45 VARCHAR2(240)
QUALIFIER_ATTRIBUTE46 VARCHAR2(240)
QUALIFIER_ATTRIBUTE47 VARCHAR2(240)
QUALIFIER_ATTRIBUTE48 VARCHAR2(240)
QUALIFIER_ATTRIBUTE49 VARCHAR2(240)
QUALIFIER_ATTRIBUTE50 VARCHAR2(240)
QUALIFIER_ATTRIBUTE51 VARCHAR2(240)
QUALIFIER_ATTRIBUTE52 VARCHAR2(240)
QUALIFIER_ATTRIBUTE53 VARCHAR2(240)
QUALIFIER_ATTRIBUTE54 VARCHAR2(240)
QUALIFIER_ATTRIBUTE55 VARCHAR2(240)
QUALIFIER_ATTRIBUTE56 VARCHAR2(240)
QUALIFIER_ATTRIBUTE57 VARCHAR2(240)
QUALIFIER_ATTRIBUTE58 VARCHAR2(240)
QUALIFIER_ATTRIBUTE59 VARCHAR2(240)
QUALIFIER_ATTRIBUTE60 VARCHAR2(240)
QUALIFIER_ATTRIBUTE61 VARCHAR2(240)
QUALIFIER_ATTRIBUTE62 VARCHAR2(240)
QUALIFIER_ATTRIBUTE63 VARCHAR2(240)
QUALIFIER_ATTRIBUTE64 VARCHAR2(240)
QUALIFIER_ATTRIBUTE65 VARCHAR2(240)
QUALIFIER_ATTRIBUTE66 VARCHAR2(240)
QUALIFIER_ATTRIBUTE67 VARCHAR2(240)
QUALIFIER_ATTRIBUTE68 VARCHAR2(240)
QUALIFIER_ATTRIBUTE69 VARCHAR2(240)
QUALIFIER_ATTRIBUTE70 VARCHAR2(240)
QUALIFIER_ATTRIBUTE71 VARCHAR2(240)
QUALIFIER_ATTRIBUTE72 VARCHAR2(240)
QUALIFIER_ATTRIBUTE73 VARCHAR2(240)
QUALIFIER_ATTRIBUTE74 VARCHAR2(240)
QUALIFIER_ATTRIBUTE75 VARCHAR2(240)
QUALIFIER_ATTRIBUTE76 VARCHAR2(240)
QUALIFIER_ATTRIBUTE77 VARCHAR2(240)
QUALIFIER_ATTRIBUTE78 VARCHAR2(240)
QUALIFIER_ATTRIBUTE79 VARCHAR2(240)
QUALIFIER_ATTRIBUTE80 VARCHAR2(240)
QUALIFIER_ATTRIBUTE81 VARCHAR2(240)
QUALIFIER_ATTRIBUTE82 VARCHAR2(240)
QUALIFIER_ATTRIBUTE83 VARCHAR2(240)
QUALIFIER_ATTRIBUTE84 VARCHAR2(240)
QUALIFIER_ATTRIBUTE85 VARCHAR2(240)
QUALIFIER_ATTRIBUTE86 VARCHAR2(240)
QUALIFIER_ATTRIBUTE87 VARCHAR2(240)
QUALIFIER_ATTRIBUTE88 VARCHAR2(240)
QUALIFIER_ATTRIBUTE89 VARCHAR2(240)
QUALIFIER_ATTRIBUTE90 VARCHAR2(240)
QUALIFIER_ATTRIBUTE91 VARCHAR2(240)
QUALIFIER_ATTRIBUTE92 VARCHAR2(240)
QUALIFIER_ATTRIBUTE93 VARCHAR2(240)
QUALIFIER_ATTRIBUTE94 VARCHAR2(240)
QUALIFIER_ATTRIBUTE95 VARCHAR2(240)
QUALIFIER_ATTRIBUTE96 VARCHAR2(240)
QUALIFIER_ATTRIBUTE97 VARCHAR2(240)
QUALIFIER_ATTRIBUTE98 VARCHAR2(240)
QUALIFIER_ATTRIBUTE99 VARCHAR2(240)
QUALIFIER_ATTRIBUTE100 VARCHAR2(240)
QUALIFIER_CONTEXT VARCHAR2(30)


JRStern

unread,
May 17, 2001, 9:06:36 PM5/17/01
to
On Thu, 17 May 2001 21:48:09 GMT, Mikito Harakiri
<nos...@newsranger.com> wrote:
>PRICING_ATTRIBUTE1 VARCHAR2(240)
>PRICING_ATTRIBUTE2 VARCHAR2(240)
...

Not even 1NF.

J.

Jeff_Bane

unread,
May 18, 2001, 3:23:42 AM5/18/01
to
I think what I enjoy most is the intuitive and descriptive naming convention
of each column.


Goran Sliskovic

unread,
May 18, 2001, 4:30:40 AM5/18/01
to

Jeff_Bane <sql...@excite.com> wrote in message
news:264N6.1386$me4....@news1.rdc1.fl.home.com...

> I think what I enjoy most is the intuitive and descriptive naming
convention
> of each column.
>
>

I think I would enjoy querying that table. Eg. select all records that have
at least one pricing_attribute not null. Would be fun.

Goran


Mikito Harakiri

unread,
May 29, 2001, 8:30:12 PM5/29/01
to
You mean that table definition becomes more compact like this

TYPE string_list_t AS TABLE OF VARCHAR2(240);

table PRICING_ATTRIBUTES (
PRICING_ATTRIBUTES string_list_t,
PRICING_CONTEXT VARCHAR2(30),
QUALIFIER_ATTRIBUTES string_list_t
QUALIFIER_CONTEXT VARCHAR2(30)
}

right? Hey, this is not funny any more. People still would question if we could
query such a table, and if the application program around it would be readable,
but is not as strikingly stupid as the original. It is amaising how
arrays/collections are able to hide design ridicule, though. Maybe this is why
relationists dislike traditional programming fetures;-)


In article <ZvWQ6.4556$rn5.2...@www.newsranger.com>, Vadim Tropashko says...
>
>That was clearly written before nested tables and other modern stuff arrived.
>The question is if one would code this with nested table (aka array), would it
>make the design less stupid?
>
>In article <tGXM6.6343$6j3.5...@www.newsranger.com>, Mikito Harakiri says...


>>
>>Name Null? Type
>>------------------------------- -------- ----
>>PRICING_ATTRIBUTE1 VARCHAR2(240)
>>PRICING_ATTRIBUTE2 VARCHAR2(240)
>>PRICING_ATTRIBUTE3 VARCHAR2(240)
>>PRICING_ATTRIBUTE4 VARCHAR2(240)
>>PRICING_ATTRIBUTE5 VARCHAR2(240)
>>PRICING_ATTRIBUTE6 VARCHAR2(240)
>>PRICING_ATTRIBUTE7 VARCHAR2(240)
>>PRICING_ATTRIBUTE8 VARCHAR2(240)
>>PRICING_ATTRIBUTE9 VARCHAR2(240)
>>PRICING_ATTRIBUTE10 VARCHAR2(240)

>> ... 90 more
>
>


Vadim Tropashko

unread,
May 29, 2001, 8:43:57 PM5/29/01
to
Job adverticement:

Need marsalling-unmarshalling programmer for Pricing Attributes.
Knowledge of modern technologies desirable, but not requred. Ideal candidate
must have significant experience calling functions with 200 arguments or more.

In article <tGXM6.6343$6j3.5...@www.newsranger.com>, Mikito Harakiri says...
>

Topmind

unread,
May 30, 2001, 12:25:06 AM5/30/01
to

> You mean that table definition becomes more compact like this
>
> TYPE string_list_t AS TABLE OF VARCHAR2(240);
>
> table PRICING_ATTRIBUTES (
> PRICING_ATTRIBUTES string_list_t,
> PRICING_CONTEXT VARCHAR2(30),
> QUALIFIER_ATTRIBUTES string_list_t
> QUALIFIER_CONTEXT VARCHAR2(30)
> }
>
> right? Hey, this is not funny any more. People still would question if we could
> query such a table, and if the application program around it would be readable,
> but is not as strikingly stupid as the original.


> It is amaising how
> arrays/collections are able to hide design ridicule, though. Maybe this is why
> relationists dislike traditional programming fetures;-)
>

Indeed. Managers can often follow and see the structure
of a RDBMS setup, but would rarely touch an array.


>
> In article <ZvWQ6.4556$rn5.2...@www.newsranger.com>, Vadim Tropashko says...
> >
> >That was clearly written before nested tables and other modern stuff arrived.
> >The question is if one would code this with nested table (aka array), would it
> >make the design less stupid?
> >


Are you saying that one cannot fix (normalize) the table?
That is the first thing I would try to do. However,
jillions of programs may reference it in its current
(nasty) state.

Hey! I got a brilliant idea! Turn it into an OO class
with 90 set/gets! Just kiddin'.


> >In article <tGXM6.6343$6j3.5...@www.newsranger.com>, Mikito Harakiri says...
> >>
> >>Name Null? Type
> >>------------------------------- -------- ----
> >>PRICING_ATTRIBUTE1 VARCHAR2(240)
> >>PRICING_ATTRIBUTE2 VARCHAR2(240)
> >>PRICING_ATTRIBUTE3 VARCHAR2(240)
> >>PRICING_ATTRIBUTE4 VARCHAR2(240)
> >>PRICING_ATTRIBUTE5 VARCHAR2(240)
> >>PRICING_ATTRIBUTE6 VARCHAR2(240)
> >>PRICING_ATTRIBUTE7 VARCHAR2(240)
> >>PRICING_ATTRIBUTE8 VARCHAR2(240)
> >>PRICING_ATTRIBUTE9 VARCHAR2(240)
> >>PRICING_ATTRIBUTE10 VARCHAR2(240)
> >> ... 90 more
> >


Isn't there also 90 "QUALIFIER_ATTRIBUTES" snipped out?


> >
>
>
>

-T-

Topmind

unread,
Jul 21, 2001, 11:12:22 PM7/21/01
to

This message is at least a month old. Why is it popping
back up now?

Aliens?

-T-

Mike Mohr

unread,
Jul 22, 2001, 6:16:46 PM7/22/01
to
Topmind wrote:

> This message is at least a month old. Why is it popping
> back up now?
>

One possibility is an attack of Magistrate virus against an Outlook client. The result
is a message to everyone in the user's address book (including USENET groups) with a
segment of an earlier message or saved text as the message.

================================================================
Mike Mohr, Systems Administrator === Email: Mike...@aut.ac.nz
Information Technology Group === Phone: 64 9 917-9999 x8133
Auckland University of Technology === Fax: 64 9 917-9901
PO Box 92006, Auckland, New Zealand =
http://home.aut.ac.nz/staff/mmohr/
================================================================
Chaos reigns within. Repent, reflect, reboot. Order shall return.


Steve Long

unread,
Jul 27, 2001, 8:25:08 AM7/27/01
to
i infer from your reaction to this that you are relatively new to this
industry. i have seen much, much worse, believe me. at least these columns
have human readable names.

"Mikito Harakiri" <nos...@newsranger.com> wrote in message
news:tGXM6.6343$6j3.5...@www.newsranger.com...

0 new messages