Client filtering not working in an example similar with JPA Relation OneToMany

[mpretorian]

Hi,

I'm testing with smartgwtpower-3.1p.2013-07-03.

I changed a bit the jpaRelationOneToMany example from the smartgwtee showcase. See the attached files and pictures.

I tested the filtering based on the Cities field, using the filter bar.
I found that filtering doesn't work well, especially after all countries are fetched to the client.
When I configured the country grid to not filter on client then the filtering worked well.

Could you please check if there is a bug in the framework or a wrong usage of the components/datasource?

Thank you,
Mihnea

[Isomorphic]

This is likely something to do with textMatchStyle - please show the request from the dev console

[mpretorian]

I get no request in dev console when filtering form the filter bar.
See the attached files taken from the console.
Btw, I attached previously all needed files for testing.
I takes too long for me when only I do the testing.

[Isomorphic]

We see the issue and will address it in the next day or so

[Isomorphic]

This has been fixed - the changes will be in nightly builds of July 11 and later

[mpretorian]

Is the same feature also available to SQL datasources?
I tried and it didn't work for me.
I would like to use such SQL datasource:

<DataSource
  ID="countryOneToManySQL"
  serverType="sql"
  tableName="country"
>
  <fields>
    <field name="countryId"/>
    <field name="countryCode"/>
    <field name="countryName"/>
    <field name="cities" hidden="false" multiple="true" 
            foreignKey="cityOneToManySQL.cityId" 
            optionDataSource="cityOneToManySQL" displayField="cityName" valueField="cityId" 
    />
  </fields>
</DataSource>

and be able to fetch countries by cities IN [1,2] and have the framework generate the EXISTS where expression like in JPA case.
Fetching along with the country details also the cities ids would be even better.

[Isomorphic]

The client-side filtering issue you reported is fixed for any DataSource.

SQLDataSource doesn't currently generate the kind of SQL you're looking for when IDs are used as filter values against a many-many relation field. If you're interested in this (and/or the related features you hinted at), consider Feature Sponsorship.