On Sat, Feb 16, 2008 at 09:15:24AM -0500, Tom Lane wrote:
> Does it have to be a typedef, rather than a #define?
> I'm thinking that you could forcibly include sys/types.h
> and then it would be safe to #define dtime_t the way you want.
I just committed a patch that does more or less what you sugg
Michael Meskes <[EMAIL PROTECTED]> writes:
> Anyway, does anyone have a suggestion how to solve this issue? Informix
> uses the dtime_t datatype to store a timestamp. pgtypeslib also defines
> a timestamp type which is 64 bit and not 32 bit like the NetBSD one.
> Informix compatibility now typedefs
On Fri, Feb 15, 2008 at 05:07:17PM -0500, Kris Jurka wrote:
>> Could anyone please tell me how NetBSD defines dtime_t? We have a
>> buildfarm failure on canary.
>
> /usr/include/sys/types.h says:
>
> typedef int32_t dtime_t;/* on-disk time_t */
Thanks. I wonder why they define this
On Fri, 15 Feb 2008, Michael Meskes wrote:
Could anyone please tell me how NetBSD defines dtime_t? We have a
buildfarm failure on canary.
/usr/include/sys/types.h says:
typedef int32_t dtime_t;/* on-disk time_t */
Kris Jurka
---(end of broadcast)--
Could anyone please tell me how NetBSD defines dtime_t? We have a
buildfarm failure on canary. I know which change triggered this. I
enabled
typedef timestamp dtime_t;
Which was mishandled by ecpg in Informix mode before and didn't work at
all if you were using the data type.
Michael
--
Michae
