Hello,

What is the planning of different version ?

Each 6 month: april and october ?

a+
Vicnet

Hi Vicnet,

There is no formal planning.
The criterias to do a new versions are:
- Is the change log enough important?
- Do we have critical bug corrected?
- Did a user request a new version?
- Do I have time to do it?

I think I will do a new version. May be this week-end.

Regards.

Hi Vicnet,

I published the 1.11.0 version.

Regards.

Hello,

Thanks, installed and file converted.

Thanks also for creation date, but it should be filled with same date as operation during convertion, should it ?

Remark: in bug tracker, 1.10 is not available, not 1.11.
(in some skrooge sites, also 1.10 or 1.11 is missing, I will report here if I found someone)

a+
Vicnet

For creation date, I use this sql command to set pseudo creation date:

Code: Select all

UPDATE operation SET d_createdate = d_date || ' 12:00:00' WHERE d_createdate = '2015-04-09 12:14:52'

where the last date/time is one used when migratation has been done.

a+
Vicnet

vicnet wrote:Hello,
Thanks also for creation date, but it should be filled with same date as operation during convertion, should it ?

Why? The operation date is not the creation date. I decided to initialized the creation date with the date of creation of this new attribute, so the migration date.

smankowski wrote:Why? The operation date is not the creation date. I decided to initialized the creation date with the date of creation of this new attribute, so the migration date.

Because when you group operations by creation date, you have a big number of operation in only one group !
Generally, you create an operation with current date or near the current date so it is better to use operation date for creation date if not set.

Actually, it is not a big problem. I patch my database directly.

a+
Vicnet