This is a different issue. It looks like the issue is that we are getting a datetime object back which is fully a timestamp. This may need to be corrected on the db side.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This was fixed by moving portions of the screen to the elements.html framework and casting the validto to date from timestamp.
The reason we went to timestamps in the first place was to get access to the special value of infinity. There's no reason to support times other than midnight here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a different issue. It looks like the issue is that we are getting a datetime object back which is fully a timestamp. This may need to be corrected on the db side.
svn 6458
This was fixed by moving portions of the screen to the elements.html framework and casting the validto to date from timestamp.
The reason we went to timestamps in the first place was to get access to the special value of infinity. There's no reason to support times other than midnight here.