Les Hazlewood wrote:
Whats wrong with doing:
public boolean isValid(Mapping mapping) {
try {
validate(mapping);
} catch (MappingException me) {
return false;
}
return true;
}
?
> (we could implement isValid(Mapping) in terms of validate(Mapping).
That line was e
Title: RE: [Hibernate] Better validate on property and value ?
Whats wrong with doing:
public boolean isValid(Mapping mapping) {
try {
validate(mapping);
} catch (MappingException me) {
return false;
}
return true;
}
?
At least that way you get the add
Hi!
Should we not make a validate(Mapping) on property and value which
throws appropiate exceptions (especially with a more precise message)
the the current on in ClassPersister which just call's isValid() and
assumes it has soemthing to do with number of columns
Any reasons/arguments agai
I have some tables in my hibernate mapping that I am in not
control of. However, I like being
able to automatically create and change (drop and recreate) my tables. It saves
a ton of time. With the tables that
I am not in control of (and have mappings to) I have run into a problem. In or
