Hello,

I am wondering how Mantis uses unix_timestamp generally enough so that
is works with all databases. I need to support Scmbug integrating with
Mantis 1.2.0 properly, and I am not sure how I should do that. 

Currently, Scmbug issues SQL statements directly to the Mantis database
for its integration, due to a lock of a general API that could be used
from Perl.

Thanks for any help.
Kristis

-------- Forwarded Message --------
From: Kristis Makris <[email protected]>
To: Martin Fuchs <[email protected]>
Cc: [email protected]
Subject: Re: [scmbug-users] Scmbug and Mantis 1.2.0
Date: Sun, 07 Mar 2010 15:49:39 -0700

Martin, unix_timestamp() is not available for postgres, or other
databases. I am not sure what is the best way to handle this. I wonder
how the Mantis developers handle it.

On Sun, 2010-02-28 at 11:29 +0100, Martin Fuchs wrote:
> Hello,
> 
> there is now the new Mantis release 1.2.0:
> 
> http://www.mantisbt.org/
> 
> 
> One change includes this:
> 
> - Migrated away from DATETIME fields to integer timestamps for timezone usage
> 
> To become compatible to this new version, Scmbug should be changed to set all 
> date fields to unix_timestamp() instead of now() when inserting new rows in 
> the Mantis MySQL database.
> 
> 
> Regards,
> 
>     Martin
> _______________________________________________
> scmbug-users mailing list
> [email protected]
> http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users

Reply via email to