String References in C#

Question

this is my first post.

I am selecting some fields from a database which are numeric id values e.g. 10,20,100,110 etc. These numbers actually mean something meaningful such as area. Ideally there should be a look up database table with matching ID and name field but there isnt and it has now become difficult to implement in a reasonable timescale (politics).

I currently use a cumbesome switch function to check the id and return the relevent text.

private string GetUnitName(string areaid)
{
    string areaName = string.Empty;
    switch (areaid.Trim())
    {
        case "10":
            areaName = "area 1";
            break;
        case "20":
            areaName = "area 2";
            break;
        case "30":
            areaName = "area 3";
            break;
    }
    return areaName ;
}

I cant get them in a dateabse so what is the best way to store these area strings?
Can I group them in a settings file or something?

Thanks for listening

score 4 · Answer 1 · edited Dec 02 '09 at 08:36

4

You could store them as an enum:

public enum Areas
{
    [Description("Area 1")]
    Area1 = 10,
    [Description("Area 2")]
    Area2 = 20,
    [Description("Area 3")]
    Area3 = 30
}

Areas x = Areas.Area1;
string xName = x.ToString();

edited Dec 02 '09 at 08:36

H H

263,252
30
330
514

answered Dec 02 '09 at 08:28

cjk

45,739
9
81
112

Where is this DescriptionAttribute located? I can only find it in ms.vs.TestTools.UnitTesting, and is only allowed on methods. – Hans Keﬆing Dec 02 '09 at 10:00
@Hans - System.ComponentModel.Description. You could also create your own Description attribute. – cjk Dec 02 '09 at 14:13

score 3 · Accepted Answer · answered Dec 02 '09 at 08:34

As an Enum you'd have to recompile if you ever needed to change them (depends how often they change)?

Alternatively you could just have a XML Document that you could stash in the Cache and XPath it to find the text for the id?

<Areas>
  <Area id="10">Area 1</Area>
  <Area id="20">Area 2</Area>
  <Area id="30">Area 3</Area>
</Areas>

XPath: /Areas/Area[@id='<your id here>']

Set the Cache Dependancy to expire if the file is changed then when you update it you won't have to restart anything. For speed you could read this into memory as a hash so you don't have to keep XPathing the doc all the time too.

score 1 · Answer 3 · answered Dec 02 '09 at 08:33

1

Can you then not rather store them in an XML file and dynamically load them on startup/data refresh. This way you can create the framework for later change to a database table.

answered Dec 02 '09 at 08:33

Adriaan Stander

162,879
31
289
284

score 0 · Answer 4 · answered Dec 02 '09 at 08:31

0

You could make an object containing the Id and the Text, and you might find better ways to refactor from there.

Edit: and store them in a List somewhere, of course :)

answered Dec 02 '09 at 08:31

Jimmeh

2,834
1
22
21

score 0 · Answer 5 · edited May 23 '17 at 10:27

0

You might want to consider Enumeration Classes to give you most of the benefits of enums, but still allow you to extend the implementation as you see fit (such as adding your own method of persistence and caching as suggested in some of the other answers to this question).

There's some more info in a question I asked about enums.

edited May 23 '17 at 10:27

Community

1
1

answered Dec 02 '09 at 08:49

rohancragg

5,030
5
36
47

score 0 · Answer 6 · edited May 23 '17 at 12:02

In terms of code storage I would consider Dictionary and KeyValuePair, which makes lookup easy and quick. Assuming you're talking about a quantity of data that can be handled in memory that is.

See Best implementation for Key Value Pair Data Structure?

Then you could load the store from a file. XML would be a good way, although if it really is just plain ID and string value, then a simple CSV text file would suffice.

If you are talking a huge amount of data however then it may be better looking into a random access kind of file storage, but then the time taken to do this may be better spent with a database.

On the other hand, if it's just a handful of data items and these are guaranteed not to change, then as others have mentioned, an enum would be fine.

String References in C#

6 Answers6