Hello Arì!
I was reading the thread, and then come to my mind a technique I was
using in such cases where the database has more advanced fields than
what is possible with Delphi.
I always use TDateTime usually because it is very standard and
painless to work with. I can switch the database backend with no
problems. I like it.
But when I want some very specific information from the database that
i can't get from a standard TDatetime (for example, I'm always using
PostgreSQL that I like a lot, the timestamp can contain localized
information, but not the TDateTime format) so what I do is that in my
SQL query I'm casting the type to another type, like a string, so that
I can proces the information manually by myself when required. This is
always working because the casting of the database is standard.
Now this is valid for PostgreSQL RDBMS, and since I don't know about
DB2, I'm wondering if casting the field type to another type in the
SQL statement could be a solution for you? So you could use standard
TDateTime when not required, or some casting when you need very
precise information.
Hope this can help you.
Best regards.
2006/4/4, Arí Ricardo Ody <[EMAIL PROTECTED]>:
> Alright Michael. The fact is that there is tables
> that have TIMESTAMP columns with more than 3
> digits of fraction... I'm trying to say that I
> think that you can't ignore it with simplicity. Or can you?
>
> I trying to explain since this discussion starts
> that, at least, Lazarus/FPC can be able to handle
> 6 digits of fraction. Otherwise in can't process
> tables generated from some other languages(cobol,
> for example). Or you can create a Lazarus/FPC TIMESTAMP version.... :-[
>
> [ ]
>
> Ricardo
--
Alexandre Leclerc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
