Date field with sqlStorageStrategy="number" shows 11/30/02 when column value is zero

[jay.l.fisher]

Is there some way to have zero in this case be converted to null?

[Isomorphic]

Could you clarify which direction you're talking about - are you saying that if you have the value 0 stored in the column, a "fetch"/SELECT turns it into this particular date value?

[jay.l.fisher]

Yes. When the column value in the database is zero, the UI displays 11/30/02. The DSResponse has, for example,

requestedToShipOn:new Date(-2117080800000)

[Isomorphic]

Well, null would definitely be better than a bizarre date in 2002 :) We'll look at changing this but it will be probably early next week.

[jay.l.fisher]

Thanks. FYI - it appears to be on both the 2.5 and 3.0 releases.

[Isomorphic]

This change will be present in the next nightly (2.5p, 3.0p and 3.1d).

The behavior is:
1. 0 becomes null (without a warning)
2. anything else that's not a valid date code is warned about and then becomes null

[ecruz]

Hi, I've just downloaded the 1/12 and 1/3 Power edition jars (v 3.0p), and it seems that the issue is still there -- 0 dates are being displayed as 11/30/02. Should the fix have been available in these builds? If not, when will it be available? Thanks.

[Isomorphic]

Sorry, we're revising it a bit to handle leading 0s in number columns. Right now it's just 3.1d.

[ecruz]

Hi --

Was this fix ever released into other SmartGWT versions?

Thanks.

[Isomorphic]

Yes, 3.0p and 3.1d.