Hi,

I'm stuck with an apparently simple problem.

I have two classes : A and B.

I'm using a single-table-per-class-hierarchy with discriminator column and default value (column is DTYPE and value is either 'A' or 'B').

When I try to fetch, with a named query - "from A" , all As, I get all Bs too (normal).

What I need is only A instances.

How can I do that with annotations (I didn't found the answer) ?

Thanks in advance for your help,

sne.

What I used was

as described by
http://forum.hibernate.org/viewtopic.php?t=961213

you mean B is a subclass of A?
You can't and shouldn't try then
B is a A by definition
If you want A and not B, then your object design is wrong, you should redesign it maybe by using delegation

Ho, well, let me explain a little bit more what my problem is.
I have two classes "SimpleCustomer" and "SpecialCustomer", which extends "SimpleCustomer" and add some properties.
We may persists SimpleCustomers and SpecialCustomers, depending on the type of the customer.

But when I want only SimpleCustomer on the screen "Ol' Barney Store Simple Customer's list", I don't want to fetch from the DB SpecialCustomers too !

Why fetching datas I'm not interested in ? Do I have to fetch everything and sort later to remove from the result uninteresting objects ?
Or did I * really* missed something ? ;)


By the way : let's say that I saved a "SpecialCustomer" and, later on, am only interested by his "SimpleCustomer" properties for a use case (some 'condensed' view that show only all common properties for all Customers).

Must I :
- fetch my "SpecialCustomer"s, cast them into "SimpleCustomer"s and return them as is => useless datas will be fetched then ;
- use a very powerful feature of Hibernate I didn't found yet that can transtype my "SpecialCustomer" into a "SimpleCustomer" without complicated query ? (please note that I use a table-per-class-hierarchy with a discriminator column).

Thanks in advance for your aswers,

sne.[/list]

I would
use a projection query which can be a select new SimpleObject(...)
or put my special data in a specific table and use delegation
or use the lightweight pattern( see the wiki community area)
or use bytecode enhancement and lazy property (@Basic(fetch=LAZY))

decreasing preferences