Thanks
-- Ashesh
On Wed, Nov 28, 2012 at 10:10 PM, Dave Page wrote:
> Thanks, patch applied.
>
> On Wed, Nov 28, 2012 at 12:20 PM, Ashesh Vashi
> wrote:
> > Hi All,
> >
> > We found an issue related to using wxDatePickerCtrl instead of
> > wxCalendarBox.
> > Actually - wxDatePickerCtrl does save
Thanks, patch applied.
On Wed, Nov 28, 2012 at 12:20 PM, Ashesh Vashi
wrote:
> Hi All,
>
> We found an issue related to using wxDatePickerCtrl instead of
> wxCalendarBox.
> Actually - wxDatePickerCtrl does saves the time too, and that's why while
> using it, it also add up time from the control i
Date picker controls returns a full timestamp by
default, which can cause inadvertent date changes
on jobs and role validty dates. Ignore the time part.
Branch
--
REL-1_16_0_PATCHES
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=d66e3ff7469707cfa5c27b75af9e478f
Date picker controls returns a full timestamp by
default, which can cause inadvertent date changes
on jobs and role validty dates. Ignore the time part.
Branch
--
master
Details
---
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=35666a65fe3ec3b486e11cc36947fab034f9e8a0
Aut
Hi All,
We found an issue related to using wxDatePickerCtrl instead of
wxCalendarBox.
Actually - wxDatePickerCtrl does saves the time too, and that's why while
using it, it also add up time from the control in update SQL(s).
Because of that, the following scenario happens:
- Create a job 'a'
- Cr