While you don't mention which RDBMS system you will be using, I've recently ventured into the C API for MySQL and used the TIMESTAMP data type.
From what I recall of it, it doesn't handle milliseconds either.
If it is an absolute necessity to record those milliseconds, you could continue to use what you already have to convert the major part of that new time string but add a column to the relevant table to hold the milliseconds part. This new column could default to 0 for logs that don't contain millisecond information.
One advantage might be that existing code for previous log formats won't need to be disturbed but you would need to check the value of this column when reconstructing the timestamp.
In reply to Re: Timestamp help
by LesleyB
in thread Timestamp help
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |