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
Major bug in saving second value in Timestamp attribute
Major bug in saving second value in Timestamp attribute
From,
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
-
- Posts: 1471
- Joined: Tue Jan 24, 2017 5:51 am
- Location: 'Stralya
Re: Major bug in saving second value in Timestamp attribute
I think this is a documented MySQL limitation
Re: Major bug in saving second value in Timestamp attribute
Thanks PW for the response.
Currently I am using MS SQL Express edition. Does this is a limitation of AwareIM or Database ?
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
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
-
- Posts: 1471
- Joined: Tue Jan 24, 2017 5:51 am
- Location: 'Stralya
Re: Major bug in saving second value in Timestamp attribute
Ah, don’t know about MSSQL. Sorry.
Re: Major bug in saving second value in Timestamp attribute
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:
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:
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
Jaymer
Aware Programming & Consulting - Tampa FL
Re: Major bug in saving second value in Timestamp attribute
Thanks Jaymer for confirming.
Waiting for support response...
Waiting for support response...
From,
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
-
- Posts: 7559
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Re: Major bug in saving second value in Timestamp attribute
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
Re: Major bug in saving second value in Timestamp attribute
Thank you very much.
It works like charm!
It works like charm!
From,
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL
Re: Major bug in saving second value in Timestamp attribute
Hi,
Can anyone confirm that this is a limitation in MySQL? If not how can I store seconds on a timestamp in MySQL?
Thanks
Can anyone confirm that this is a limitation in MySQL? If not how can I store seconds on a timestamp in MySQL?
Thanks
Re: Major bug in saving second value in Timestamp attribute
Hi,
Can you try to change the datatype DATETIME to DATETIME(3)?
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
Himanshu Jain
AwareIM Consultant (since version 4.0)
OS: Windows 10.0, Mac
DB: MYSQL, MSSQL