Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

Lookup Table Design Expand / Collapse
Author
Message
Posted Friday, October 19, 2007 6:42 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, April 10, 2009 12:04 PM
Points: 27, Visits: 90
The meaning of a code is entirely subjective and has nothing to do with normalization ... it might actually be a picture or several pictures or an mp3/mp4
Post #412746
Posted Friday, October 19, 2007 9:02 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, February 14, 2014 11:35 AM
Points: 57, Visits: 75
roger clarke (10/19/2007)
The meaning of a code is entirely subjective


If you have a code WHS123 that is a 'local distribution warehouse', it may have many translations into local languages, but is is entirely objective. You would not want one application to reference this as a 'regional manufacturing warehouse' and another calling is 'building xyz' because that is what they think it should be called. If both of those are also accurate descriptions of WHS123 that are synonymous to the actual meaning, they too can be stored in the database.



- Jay
Post #412852
Posted Saturday, October 20, 2007 5:56 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, April 10, 2009 12:04 PM
Points: 27, Visits: 90
objective=0|1 (digital) subjective=analog ... you have missed the entire point
Post #413076
Posted Saturday, October 20, 2007 6:22 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, February 14, 2014 11:35 AM
Points: 57, Visits: 75
I am trying to understand the point of letting the GUI do the translating.

For instance, I have a database that contains the transactional data for one of the systems operating the business. There are actually two applications that operate primarily in this database. There are two others that store ancillary (to those systems) data there. There are also at least three different reporting platforms. Additionally, there could be any number of home-brewed reporting apps in Access or Excel.

In such a scenario, when a code description changes, would you want to make that change once in a database. Or, would you prefer to update that code in every application that references it? Or, maybe make the change in one of the systems and let the others fall out of date?

The point is that this data describes entities in your database and they belong in that same database for the sake of data integrity.



- Jay
Post #413121
Posted Sunday, October 21, 2007 8:14 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, April 10, 2009 12:04 PM
Points: 27, Visits: 90
With apologies to Elizabeth Barrett Browning ... Let me count the ways

There are two things here ... a real problem and a suggested solution

the problem is ... the infinite no of translations of any word or phrase (even in the same language ... Mr John S Jones, jonny boy, Mr Jones)

the (extremely vague) solution is ... let the GUI figure it out
Post #413182
Posted Sunday, October 21, 2007 1:02 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, February 14, 2014 11:35 AM
Points: 57, Visits: 75
Why can the user preferred names be saved in the database with the 'official' versions of the names? Why would you trust a number of GUI's to translate everything consistently?

You still have not defended your position of why the GUI should have the translations versus keeping that data (not matter how customizable) in the database. You have merely stated that the GUI would be better than the database. Why?



- Jay
Post #413206
Posted Wednesday, October 15, 2008 7:05 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, October 15, 2008 6:59 AM
Points: 1, Visits: 0
Interesting topic but I am dumbfounded by the table and field naming conventions used in the examples given.
It makes the article really difficult to read.
Post #586154
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse