Re: GDA_Date??

[cwiegand startek com (Chris Wiegand)]

BTW, Vivien, where are the conversion routines (ie. converting from
Postgres types to GDA and back? I tried to find them to see how they did
it, and couldn't find them.) ?

Also, is there a definitive list of what functions do what (ie.
gda_mysql_connectdatabase is a public function, and does yadayada, but
gda_mysql_foo_bar is a private function specific to mysql, and does
whatever the author made it do)? I'm wondering because I'd like to document
and/or know what the functions in the mysql server do, and I understand
some of them, but not all of them yet. Just wondering here.

At 08:44 PM 4/5/00 +0200, Vivien wrote:
>> > >> I'm fixing up some stuff in the MySQL server as far as date/time
handling,
>> > >> however, I can't seem to figure out what GDA_Date is...it appears
to be a
>> > >> long value, however, it isn't documented what that is (ie. GDA_Date ?=
>> > >> seconds since epoch, GDA_Date ?= seconds since 1900?). I figured
other the
>> > >> others, they're pretty straightforward. :)
>> > >>
>> > >
>> > >It is a long value, but its contents are not yet specified. This is
one of
>> > >the values that is missing, so what suggestions you've got for this
type?
>> > >What should it contain?
>> >
>> > Hmm....I'm thinking a long value of the seconds since 1/1/70 12:00 UTC
>> > (aka. the time_t thing, although that might be the struct, it's been a
>> > month since I've used it...) That is a pretty standard time-like variable
>> > used in programming, and is easier for programs to work with than a
string
>> > (there are date/time functions in, hm.. stdlib.h or unistd.h or time.h, I
>> > think).
>> 
>> I vote as well for time_t-like values. Vivien? Stephan? Nick?
>
>Yep! I do agree with this. I'll update Postgres the week after next week when
>I'm back to work.