如何理解java中的映射概念,一对一映射的概念。解释映射

How to define a One-to-One relation between 2 classes ? I think I am going wrong somewhere,conceptually. I don't know what ,but it is.

Let us suppose there are two classes named Country and PM :

Country

int c_id

String name_c

PM

int c_id

String name_pm

Now for one country, there can only be one PM and PM can belong only to one country. How do I do this in my mapping file ?

I was trying this :

But this effete mapping does nothing than to produce an exception during run time.It says the property name_pm cannot be found inside the Country class ! But does it search inside the Country class. It should rather search inside the PM class.

Also help me accomplish my one-to-one mapping between the 2 classes. I have been trying this for some time.

Java Code:

Country

public class Country {

private int c_id;

private String name_c;

public int getC_id() {

return c_id;

}

public void setC_id(int c_id) {

this.c_id = c_id;

}

public String getName_c() {

return name_c;

}

public void setName_c(String name_c) {

this.name_c = name_c;

}

}

PM

public class PM {

private int c_id;

private String name_pm;

public int getC_id() {

return c_id;

}

public void setC_id(int c_id) {

this.c_id = c_id;

}

public String getName_pm() {

return name_pm;

}

public void setName_pm(String name_pm) {

this.name_pm = name_pm;

}

}

解决方案

If part of your question is also "...I think I am going wrong somewhere,conceptually... ", I'd like to provide some explanation.

First of all, One-to-One means, that the reference is between objects (instances). Other words, there must be reference from one object to other. Not only a common simple type (i.e. String name_pm or String name_c)

Both objects should reference each other:

public class PM {

private Country country; // reference to an instance of the PM

...

}

public class Country {

private PM pm; // reference to an instance of the Country

...

}

On a DB level, it is a bit more trickier. Because references are based on ID columns and we do assure us, that these two Country-PM will always belong together, we have to reuse the ID value.

So, one object will play the role of the Master, e.g. Country and the second will assign its ID based on it. If we won't follow that pattern, we cannot be sure, that there will sooner or later arise some many-to-one or many-to-many relation.

And that's why the mapping usually looks like this

country

But one-to-one mapping is really very exceptional. I guess that mapping many-to-on on PM side (with country id reference in DB) could be more suitable. It is different approach at all, but...

Please, try to see this nice article: