hbm2java problem with properties that have unique="true

webgineers · **Posted:** Mon Feb 23, 2004 6:52 am

Hi!

Even if a property has the unique="true" attribute, the autogenerated finder always returns a list.

max · **Posted:** Mon Feb 23, 2004 5:16 pm

yes - to avoid complexity and what if you have more than one property in the finder ?

p.s. unique and not-null is more a hint to the schemaexport tool than hints to hibernatecore or hbm2java.....but if you want you are welcome to add a JIRA request for it...even better provide a patch ;) (even though I like the simplicity of the current implementation that don't prevent anything vital as I see it...but I'm willing to be proved wrong ;)

webgineers · **Posted:** Mon Feb 23, 2004 10:34 pm

I understand the intended SchemaExport use, but it would be nice to broaden it. Poluting the app with code like this:

Code:

List list = AbcFinder.findXyz(session, value);
if (!list.isEmpty())
{
    Abc found = (Abc)list.get(0);
    // some code
}

compared to the cleaner:

Code:

Abc found = AbcFinder.findXyz(session, value);
if (found != null)
{
    // some code
}

makes no sense to me.

So, I'll submit a request to JIRA and I'll try to provide a patch. It should be pretty easy to do, but probably I would have to add a <param/> to the BasicRenderer for backward compatibility.

ianh · **Joined:** Thu Dec 16, 2004 9:00 am **Posts:** 5

Reviving this topic - did this ever make it into the production release?

max · **Posted:** Thu Dec 16, 2004 1:30 pm

i don't remember receiving a jira request/patch for it...so no.