Re: Java Enumeration Parse results to Database

Joe S wrote:


It'd help to have a sample of the code representation of what you mean by "to
enumerate", but I'll take a stab from general principles.

Any errors in interpretation you'll have to correct by being more specific.

Let's say by "to enumerate", you mean something different from what most Java
programmers would assume, "to represent as a Java 'enum'".

I'm guessing you mean something off the wall like, "split into relevant chunks
of meaning (i.e., translate into terminology I care about)".

Otherwise your question makes no sense and you need to do a better job of
asking questions. (The conclusion can be true even if the assumption doesn't
hold.)

So that terminology of interest is what we in the programming biz call a
"model". Let's say you want to model a business customer's operation. Acme
Wine Cooperative scans the Web for good wine deals and assembles them for
perusal. They use terms like "case", "bottle", "varietal", "sauvignon",
"Francis Ford Coppola Winery", etc.

A database these days doesn't have "records". They are based on tables,
comprising rows and columns. The terminology matters.

You should normalize the database at least to third normal form.

But data models are not object models. The data model is a formal slicing of
your raw data into minimal consistent, non-anomalous pieces. That isn't the
same as an object representation of your world.

So let's say you have a type like this:

public interface Wine
{
   enum Color { RED, WHITE, BLUSH, ROSE, ; }
   Map<Grape, Integer> getVarieties();
   Vintner getVintner();
   double getRating();
   ...
}

Obviously no one here can speak to how you cull the data to fill that type,
absent more details from you.

Presumably you'd find keywords in your data sources and extract the values to
fill such objects.

Then pushing that to a database is straightforward if you know JDBC and SQL.
Or are willing to learn it. You can use the JPA (Java Persistence API) library
to handle boilerplate transformation between the object and relational models.
Such libraries are called object-to-relational mapping (ORM) frameworks, and
include EclipseLink and Apache OpenJPA.

You have some studying ahead of you.

--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg