[jperin]

Hi,

I have just test with last build (v9.1p_2014-06-24/PowerEdition Deployment 2014-06-24).

This seems to be better, but not yet perfect I think.

I think there is an error with millisecond.

The filter between "between match case" does not take count of the millisecond.

If we have two records has a CreatorTimestamp like this

Record 1 with '24/06/2014 13:15:25.000' 
Record 2 with '24/06/2014 13:15:25.500' 
Record 3 with '24/06/2014 23:59:59.500'

1. If I made a filter "between (match case)" from '24/06/2014 13:15:25' to '24/06/2014 23:29:59', the record 2 is returned

If I made a filter "between (inclusive, match case)" from '24/06/2014 13:15:25' to '24/06/2014 23:29:59', the record 1 and 2 are returned

2. The record 3 is never returned


This is a bit confusing.
With the "between (match case)", can we imagine by setting the from '24/06/2014 13:15:25' to '24/06/2014 23:59:59' , the filter made this operation

'24/06/2014 13:15:25.999'<   <  '24/06/2014 23:59:59.000'

and with "between (inclusive, match case)" , can we imagine by setting the from '24/06/2014 13:15:25' to '24/06/2014 23:59:59', the filter made this operation

'24/06/2014 13:15:25.000'<=   <= '24/06/2014 23:59:59.999'

Can you have look at this.

Thanks

Julien

[Isomorphic]

Firstly, as noted earlier in this thread, our default SQL generation engine supports filtering to *second precision only*. It is not expected to include millisecond precision.

With that in mind, have you made the changes necessary to enforce millisecond precision?

Also, we're not clear on what's going wrong here - can you clarify what you mean when you say "can we imagine that..."?

Is this what you're actually seeing happen? Or what you think might be happening? Those comments don't appear to be showing actual SQL that's been generated by the SmartGWT server, right? But if so, can you show code, or logs, that demonstrate that SQL being generated?