Announcement

**Isomorphic** · 8 Jun 2012, 10:34

Code:

searchCriterion.setAttribute("value", new HashSet(Arrays.asList(new String [] {"1"})));

How did you get the idea for this line of code?? Seriously if there's some doc that you read that suggested this to you, we'd like to take a look and consider revising it.

You just need "new AdvancedCriteria(fieldName, operator, value)" and that's it.

The fieldName should be an actual fieldName, not a path to a field. If you are trying to do something like find all items within an order, then add another criteria that says the item's orderId must be equal to the ID of the order you are searching within.

**joe.parks@hyperproductive.com** · 8 Jun 2012, 10:48

I was experimenting, based on the idea from this post:
http://forums.smartclient.com/showthread.php?t=10573

In this example I'm not trying to find the items for an order. I'm trying to find orders which contain line items that have a given attribute value.

Pseudo-code:

Code:

Select Order o
Join o.lineItems AS lineItem
Where lineItem.productNumber = "655321"

**Isomorphic** · 8 Jun 2012, 11:26

You should pass the productNumber as part of the criteria for a request against the "Order" DataSource, then server-side, do something similar to your pseudocode below to retrieve the correct Orders.

If you're using SQLDataSource (the top recommendation) then that pseudocode is very nearly something you can plunk into a customized <whereClause>.

**joe.parks@hyperproductive.com** · 8 Jun 2012, 11:44

Thanks for the quick reply. I'll review both options.
I had been hoping that there was something in the criteria api to abstract the joining across datasources.

**Isomorphic** · 8 Jun 2012, 11:56

We abstract the joining across DataSources via dataSourceField.includeFrom and similar mechanisms (SQL templating) that allow you to have a field that really comes form another entity/table yet can be queried, sorted, etc as though it were a normal field of the main DataSource.

This case is a bit unusual because it's not quite a join or at any rate requires more than a straight join - your pseudocode is actually wrong as it would produce multiple copies of each order. You would need select distinct, grouping, or a sub-select to get the right result.

**joe.parks@hyperproductive.com** · 23 Oct 2012, 12:35

Originally posted by Isomorphic View Post

You should pass the productNumber as part of the criteria for a request against the "Order" DataSource, then server-side, do something similar to your pseudocode below to retrieve the correct Orders.

I'm trying to accomplish this by calling getCriteria() on the HibernateDataSource and then modifying the Hibernate Criteria object to get the results I'm looking for. Unfortunately, "getCriteria()" causes the datasource to attempt a query to retrieve the rowCount. This query throws an Exception because the underlying AdvancedCriteria/Hibernate-Criteria is not yet prepared to access the related properties.
I'll try to put together a quick testcase this evening, but is it possible to either:
1. make HibernateDataSource::buildCriteria public? and/or
2. don't make a rowCount() projection query as part of HibernateDataSource::getCriteria()?
Thanks.

**Isomorphic** · 23 Oct 2012, 13:32

Don't call undocumented methods, they aren't supported and may be moved or renamed at any time.

There doesn't seem to be a reason to access the Hibernate Criteria for this use case as far as we can tell. You can modify the default DSRequest that is passed to you before execute()ing it, or you can do additional requests via just creating a new DSRequest and setting criteria on it - the QuickStart section on using DMI for business logic has a few examples.

Announcement

Query based on values in a related collection?

Comment

Comment

Comment

Comment

Comment

Comment

Comment