Sorry about top posting but this webmail client is goofy.
I expect 100 rows for table max row count. From it I will have 5 to 7
different groups of data.
I am now bringing the entire table down in one connection to the db. <# of
connections are a big factor in that they are slow to achieve :( >
>From that initial table I am making dataviews for each grouping that my gui
>will need.
This is much faster then doing multiple selects for each group either from one
table or multiple ones.
This is currently a winForm app but my bizObjects are designed to work in web
and webservice as well.
Your "One True Lookup Table" reference was nothing close to my need, but the
name sounded similar to our conversation. I do not have to slice and dice the
Type column for relevance.
"If you make an error in the code_type or code_description among codes with the
same structure, it might not be detected. You can turn 500.000 from
{ldquo}Natural Sciences and Mathematics{rdquo} in Dewey Decimal codes into
"Coal Workers{rsquo} Pneumoconiosis" in ICD and vice versa. This can really
hard to find when one of the similarly structured schemes had unused codes in
it. "
Mine is real simple
Pkey = int (2)
my gKey is like his type = int, (1)
Description ('Regions')
For a list of all regions I "select * from table where gkey = 2"
key, gkey, Description, status, changedate, lastuser
1
0
Master
0
NULL
NULL
2
1
Sales Channel
0
NULL
NULL
3
1
Delivery
0
NULL
NULL
4
1
Regions
0
NULL
NULL
5
3
Disk
0
NULL
NULL
6
3
Pro OnLine
0
NULL
NULL
7
3
Library
0
NULL
NULL
8
2
Alldata
0
NULL
NULL
9
2
Motor
0
NULL
NULL
10
2
Midas
0
NULL
NULL
11
2
Tire Kingdom
0
NULL
NULL
12
2
Carmax
0
NULL
NULL
13
4
USA
0
NULL
NULL
14
4
Canada
0
7/17/2007 10:34:00 AM
NULL
15
4
International
0
NULL
NULL
16
4
test
-1
7/17/2007 9:41:00 AM
NULL
17
4
test2
-1
7/17/2007 8:57:00 AM
NULL
18
3
Test
-1
7/17/2007 9:49:00 AM
NULL
NULL
NULL
NULL
NULL
NULL
NULL
So you can see my types all showing up in my editing interface
select * from mytable were gkey = 1
That data is used in a combolist where the selected index change event will
repopulate the listbox for all rows with that gkey = to the cbo.SelectedValue
This is way to simple to set up and use. It's reuse is simple. I can set
another set of types later on and you could see Repair Type, length of stay,
Customer Status keeping them separate from Sales channel, region and delivery.
Having 20 to 50 different look up tables for just a description text for the
user, it's key for usage, and it's status is going to be a hard sale for me.
Having to adjust an interface with table names and column names is going to be
a RPITA. Go ahead and tell me that it's all meta data. I dare you! ;->
__Stephen
-------- Original Message --------
Subject: RE: [NF] Consulting saga continued or Why Be Normal?
From: "Mike yearwood" <[EMAIL PROTECTED]>
Date: Tue, July 24, 2007 8:40 am
To: [email protected]
I explained this same issue to Drew Speedie long ago. He had been
doing the OTLT - One True Lookup Table for years and never wondered
about it. He agreed it was probably wrong, but he didn't change the
MaxFrame samples because he had bigger fish to fry.
Normalization is not a matter of someone's opinion. I'm often amazed
how some people have conclusions about computer science theory, and,
without having any thing to verify their positions, hold to them.
Sounds like religion to me.
--- StripMime Report -- processed MIME parts ---
text/html (html body -- converted)
---
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** 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.
