wxTimePickerCtrl for GRM

[vomikan]

Revision for timing in reports.

The following syntax can be used in SQL queries:

select * from CHECKINGACCOUNT_V1 c
where c.LASTUPDATEDTIME >='&single_date'||'T'||'&single_time'

[vomikan]

It should be noted here that the time stored in the UTC time zone is not very practical.

Another unpleasant moment is that the time in the Custom dialog is saved without taking into account the time zone.

[n-stein]

You can just convert to UTC for the database read:

select * from CHECKINGACCOUNT_V1 c
where c.LASTUPDATEDTIME >= datetime('&single_date'||'T'||'&single_time', 'UTC');

[vomikan]

You can just convert to UTC for the database read:

Thanks for pointing this out.

But it's about something else. Data is saved to the database without conversion to UTC. #5533

[vomikan]

You can just convert to UTC for the database read:

select * from CHECKINGACCOUNT_V1 c
where c.LASTUPDATEDTIME >= datetime('&single_date'||'T'||'&single_time', 'UTC');

This leads me to wonder if it is necessary in this line .ToUTC() ?
value = time->GetValue().ToUTC().FormatISOTime();

[vomikan]

Transformations have to be done in 2 stages.

select c.* from CHECKINGACCOUNT_V1 c
where c.LASTUPDATEDTIME >= strftime('%Y-%m-%dT%H:%M:%S', datetime('&single_date'||'T'||'&single_time', 'UTC')) 

[vomikan]

#5533

select c.* from CHECKINGACCOUNT_V1 c
where c.LASTUPDATEDTIME >= strftime('%Y-%m-%dT%H:%M:%S', datetime('&single_date'||'T'||'&single_time', 'UTC')) 

[vomikan]

Invalid time value in the test mode of the editor.