Major bug in saving second value in Timestamp attribute

If you think that something doesn't work in Aware IM post your message here
Post Reply
himanshu
Posts: 722
Joined: Thu Jun 19, 2008 6:24 am
Location: India
Contact:

Major bug in saving second value in Timestamp attribute

Post by himanshu »

Hi Support,

We have identified a major problem in the system where we want to capture the timestamp value with following format "yyyy-MM-dd HH:mm:ss". It does not saving seconds to database or while assigning value from attribute to attribute from two objects.

If anybody else found the same issue please confirm.

Thanks
From,
Himanshu Jain


AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
PointsWell
Posts: 1457
Joined: Tue Jan 24, 2017 5:51 am
Location: 'Stralya

Re: Major bug in saving second value in Timestamp attribute

Post by PointsWell »

I think this is a documented MySQL limitation
himanshu
Posts: 722
Joined: Thu Jun 19, 2008 6:24 am
Location: India
Contact:

Re: Major bug in saving second value in Timestamp attribute

Post by himanshu »

Thanks PW for the response.

Currently I am using MS SQL Express edition. Does this is a limitation of AwareIM or Database ?
From,
Himanshu Jain


AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
PointsWell
Posts: 1457
Joined: Tue Jan 24, 2017 5:51 am
Location: 'Stralya

Re: Major bug in saving second value in Timestamp attribute

Post by PointsWell »

Ah, don’t know about MSSQL. Sorry.
Jaymer
Posts: 2430
Joined: Tue Jan 13, 2015 10:58 am
Location: Tampa, FL
Contact:

Re: Major bug in saving second value in Timestamp attribute

Post by Jaymer »

H
I just tried it on MS SQL
It does not store seconds - all timestamps end in :00 on my system - latest build v8

Interesting to note the available formats for the timestamp field do not show seconds as an option:
Screen Shot 2017-12-16 at 7.26.58 PM.png
Screen Shot 2017-12-16 at 7.26.58 PM.png (23.71 KiB) Viewed 18444 times
Click Here to see a collection of my tips & hacks on this forum. Or search for "JaymerTip" in the search bar at the top.

Jaymer
Aware Programming & Consulting - Tampa FL
himanshu
Posts: 722
Joined: Thu Jun 19, 2008 6:24 am
Location: India
Contact:

Re: Major bug in saving second value in Timestamp attribute

Post by himanshu »

Thanks Jaymer for confirming.

Waiting for support response...
From,
Himanshu Jain


AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
aware_support
Posts: 7523
Joined: Sun Apr 24, 2005 12:36 am
Contact:

Re: Major bug in saving second value in Timestamp attribute

Post by aware_support »

If you want to store seconds in SQL Server "manually" change the type of the corresponding column in the database from smalldatetime to datetime.
Aware IM Support Team
himanshu
Posts: 722
Joined: Thu Jun 19, 2008 6:24 am
Location: India
Contact:

Re: Major bug in saving second value in Timestamp attribute

Post by himanshu »

Thank you very much.

It works like charm! :mrgreen:
From,
Himanshu Jain


AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Gabbitas
Posts: 334
Joined: Sun Jan 03, 2010 3:36 am

Re: Major bug in saving second value in Timestamp attribute

Post by Gabbitas »

Hi,

Can anyone confirm that this is a limitation in MySQL? If not how can I store seconds on a timestamp in MySQL?

Thanks
himanshu
Posts: 722
Joined: Thu Jun 19, 2008 6:24 am
Location: India
Contact:

Re: Major bug in saving second value in Timestamp attribute

Post by himanshu »

Hi,

Can you try to change the datatype DATETIME to DATETIME(3)?
From,
Himanshu Jain


AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Post Reply