Re: [Sculptor] uni-directional one-to-many mapping?

Hi Patrik,

I have another question for you--
In the hbm file, to get the "key" to not say "on-delete="cascade"", we need to set this property right?

db.mysql.onDeleteCascade=false

Is this the right thing to do or is that for something else?

Also, do you have a regression test suite that tests all these different kinds of reference mappings?  I see that you have different kinds of mappings in the "library" project, but they don't seem to be broken out into tests like "one-to-many unidirectional", "one-to-many bidirectional", etc., so I am not sure what kind of coverage there is.  I just want to make sure that I don't break other mappings, because obviously there are other cases where if the design file says "inverse", we do want to output "inverse=true".

I created the JIRA here:
http://www.fornax-platform.org/tracker/browse/CSC-279

Thanks,
Polly

Patrik Nordwall wrote:

Please, add a jira bug report and we will fix it. Maybe you can solve it and supply a patch.
/Patrik