In the mapping
<class
name="ClassName" (1)
table="tableName" (2)
discriminator-value="discriminator_value" (3)
mutable="true|false" (4)
schema="owner" (5)
proxy="ProxyInterface" (6)
dynamic-update="true|false" (7)
dynamic-insert="true|false" (8)
select-before-update="true|false" (9)
polymorphism="implicit|explicit" (10)
* where="arbitrary sql where condition" (11)*
persister="PersisterClass" (12)
batch-size="N" (13)
optimistic-lock="none|version|dirty|all" (14)
lazy="true|false" (15)
/>
Tuna Toksöz
http://tunatoksoz.com
http://turkiyealt.net
http://twitter.com/tehlike
Typos included to enhance the readers attention!
On Sun, Mar 8, 2009 at 1:25 AM, flatline <[email protected]> wrote:
>
> So this can't be handled in the mapping-files? (or is there a where
> clause in the mapping definition that I am not aware of?)
>
>
> On Mar 8, 12:00 am, Tuna Toksoz <[email protected]> wrote:
> > add Where clause.
> >
> > Tuna Toksözhttp://tunatoksoz.comhttp://turkiyealt.nethttp://
> twitter.com/tehlike
> >
> > Typos included to enhance the readers attention!
> >
> > On Sun, Mar 8, 2009 at 12:05 AM, flatline <[email protected]> wrote:
> >
> > > I have a table with a discriminator column. It is a legacy database,
> > > and over time the two types of entities in the table have evolved to
> > > become so different (behaviour-wise) that I want to model them as
> > > unrelated classes. Is it possible to do this without having them
> > > inherit from an abstract class?
> >
> > > PS: modifying the DB is unfortunately not an option.
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---