[ptt-users] Milliseconds trouble with analysis data being saved in DB.

[Frank Cohen]

Dear Yurly: Thank you for pointing out the issue and proposing a  
solution. The enhancement looks good to me and I opened a ticket for it:
http://bugs.pushtotest.com/ticket/161

Our engineers are engaged on two large scale testing projects right  
now. I can't be certain when we will make the enhancement. Of course,  
if you would like to contribute a patch we would be glad to receive  
it. (And, of course, you can buy a support agreement in which case we  
will assign an engineer to this right away. Contact me at  
fcohen at pushtotest.com if this interests you.)

Thanks for your support of TestMaker.

-Frank

On Sep 14, 2007, at 7:57 AM, Yuriy wrote:

>
> Hi.
>
> We've found a trouble with analysis data being saved in DB:
>
> Unfortunately MySQL doesn't support Millisecond DATETIME Resolution  
> (see for details
> http://feedblog.org/2007/05/26/why-doesnt-mysql-support-millisecond- 
> datetime-resolution/ ), so ,for example, you can't extract  
> milliseconds from the field 'T_Start' of the 'transactions' table  
> to make an analytical chart.
>
> We can solve this bug in this way:
> Add a supplementary field of BIGINT type into 'transactions' table  
> and fill this field with datetime long value in the format  
> "yyyyMMddHHmmssSS" during saving results in a DB.
>
> Thanks.
>
> _______________________________________________
> Users mailing list
> Users at lists.pushtotest.com
> http://lists.pushtotest.com/mailman/listinfo/users



--
Frank Cohen, PushToTest, http://www.PushToTest.com, phone 408 374 7426
TestMaker: The open-source SOA test automation tool