Ok, it's patched. There were actually a few places where I was incorrectly
using java.sql.Date instead of java.sql.Timestamp. Let me know how it works
for you now.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
----- Original Message -----
From: "Oki DZ" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, August 03, 2001 2:51 AM
Subject: MailImpl (was: Re: cvs commit: jakarta-james/src/conf
spool.properties)
> On 3 Aug 2001 [EMAIL PROTECTED] wrote:
>
> > listMessagesSQL=SELECT message_name, message_state, last_updated FROM
> > <table> WHERE repository_name = ? ORDER BY last_updated ASC
>
> In MailImpl class, the lastUpdated field is intialized with the current
> date:
> private Date lastUpdated = new Date();
>
> In MySQL, when the message is stored, the content of the last_updated
> column will be just the date, without the current time (the time is set to
> zeros). I think it would be better if the store() method in
> JDBCMailRepository uses java.sql.Timestamp, so that when the message is
> stored, the time will be included. By doing so, the above SQL statement
> would be more useful. The current implementation would make the order of
> the messages to be not quite precise; the messages that are sent during
> the day would be regarded to have the same sort order. The exact order
> (the order of the messages retrieved) would be database implementation
> spesific I guess.
>
> Oki
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
----------------------------------------------------
This message was brought to you by MailHive.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
