You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Deepak Dixit <de...@hotwaxsystems.com> on 2017/05/01 10:41:37 UTC

Re: OFBIZ-3972

This has been done at r#1793300

Added generateMySqlFileWithAlterTableForTimestamps service to generate sql
alter statement for date-time and time filed.

Also update Data Migration <https://cwiki.apache.org/confluence/x/LoBr> wiki
page with revision and migration service detail.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com

On Wed, Apr 26, 2017 at 6:35 PM, Michael Brohl <mi...@ecomify.de>
wrote:

> +1 Deepak
>
> Thanks,
>
> Michael
>
> Am 15.03.17 um 05:10 schrieb Deepak Dixit:
>
> Can we conclude this?
>>
>> Thanks & Regards
>> --
>> Deepak Dixit
>> www.hotwaxsystems.com
>>
>> On Tue, Feb 28, 2017 at 2:27 PM, Rishi Solanki <ri...@gmail.com>
>> wrote:
>>
>> Interesting related blog - LINK
>>> <https://blog.sqlauthority.com/2014/02/14/mysql-when-to-
>>> use-timestamp-or-datetime-difference-between-timestamp-or-datetime/>
>>> One more conversation -
>>> http://stackoverflow.com/questions/5989539/when-to-use-
>>> datetime-or-timestamp
>>>
>>> It says it depends on the context of the field for which it is used.
>>> DATETIME seems to be good choice as we will be updating field type, and
>>> it
>>> may applicable to many places.
>>>
>>> Thanks!
>>>
>>>
>>> Rishi Solanki
>>> Sr. Manager, Enterprise Software Development
>>> HotWax Systems Pvt. Ltd.
>>> Direct: +91-9893287847
>>> http://www.hotwaxsystems.com
>>>
>>> On Fri, Feb 24, 2017 at 3:37 PM, Taher Alkhateeb <
>>> slidingfilaments@gmail.com
>>>
>>>> wrote:
>>>> I think I would prefer DATETIME. Some reasons are found here ->
>>>> http://stackoverflow.com/questions/409286/should-i-use-
>>>> field-datetime-or-timestamp.
>>>> Given that OFBiz takes care of conversions, DATETIME seems like a more
>>>> appropriate choice
>>>>
>>>> On Fri, Feb 24, 2017 at 12:13 PM, Jacques Le Roux <
>>>> jacques.le.roux@les7arts.com> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> At OFBIZ-3972 Deepak suggested
>>>>>
>>>>> <<I think we need to update fieldtypemysql.xml to honor Milliseconds.
>>>>> As we have only DATETIME set as sql type and this does not support
>>>>> Milliseconds, we need to use DATETIME(3) or DATETIME(6).>>
>>>>>
>>>>> I suggested
>>>>>
>>>>> <<Why not TIMESTAMP? https://dev.mysql.com/doc/
>>>>>
>>>> refman/5.6/en/datetime.html
>>>>
>>>>> Deepak rightly mentioned that in both cases we need to create an entry
>>>>>
>>>> in
>>>
>>>> "data migration" wiki page
>>>>>
>>>>> << we need to run alter query manually (if someone want to upgrade
>>>>>
>>>> custom
>>>
>>>> solution to latest)>>
>>>>>
>>>>> Please let know your thoughts and suggestions if any
>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>>
>
>