Your best approach probably is to normalize the table. It will make things much easier in the long run. One thing you could try it this is not an option, is to create another table called user that holds at least a primary key and the id of the users information in your parameter table. This would allow you to treat the relationship as a one-to-many and map it with hibernate. For example you could do something like the following:
Note I might have the mapping wrong I just did this off of the top of my head to illustrate the point.
@Entity
class Parameter{
@Column(name="order")
private int order;
@column(name="parameter")
private String parameter;
@column(name="value")
private String value;
}
@Entity
class User{
@column(name="id")
private int id;
@OneToMany(cascade=ALL)
@JoinTable(name="SECONDARY",
joinColumns={@JoinColumn(name="id")},
inverseJoinColumns=@JoinColumn(name="order"))
@MapKeyJoinColumn(name="parameter")
private Map<String,Parameter> userData;
public String getUserName(){
return userdata.get("user_login")
}
etc.
}