scenario
I am parsing emails and an ORM (accurate using NHibernate). While my current approach works technically, I do not like it very much, but can not solve better email has 50 ~ fields and is sent from third party and looks like this (obviously a very low dummy sample) .
field # 1: value1 field # 2: value2 field # 3: value3 field # 4: value4 field # 5: value 5 Problem
My problem is that with this parsing of many fields the database table is a full monster. I can not make any appropriate model employed in any kind or AFAIK because every email has been sent, it is all static data and does not rely on any other sources.
The only idea is that I want to find the similarities between each field and divide them into more manageable segments. Call 10 ~ Field per unit, 5 units in total, however, I do not love this idea much or I am seeing that whatever I am doing makes up one-on-one relationships.
What is a good way to manage a large number of properties beyond your control?
Any thoughts?
2 Create a table: 1 for the main object, and other fields. This way you can access each field in the program, and the object model does not look bad.
But this is only on my head; You have a strange problem.
If the data is returning to a file that you can easily parse, you may be away from creating a command line application that will produce scripts and C # that you Can execute and copy, paste in the program. I have done that when creating html pages (HTML) () outside the tables
Comments
Post a Comment