Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.org (8.9.1/8.9.1) with ESMTP id LAA19496 for ; Mon, 16 Nov 1998 11:01:36 -0500 (EST) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id AAA15830 for pgsql-interfaces@hub.org; Tue, 17 Nov 1998 00:01:37 +0800 (GMT) Date: Tue, 17 Nov 1998 00:01:37 +0800 (GMT) From: Michael Robinson Message-Id: <199811161601.AAA15830@public.bta.net.cn> To: pgsql-interfaces@hub.org Subject: RE: [INTERFACES] Updated IDL with considerations for COSS "Taral" writes: >module PostgreSQL { // Note we already separate our namespace > module Types { > typedef short int2; > typedef short int4; > // etc. > } Works for me. >> I would recommend that fixed-length PostgreSQL types be defined as little- >> endian arrays of long or octet type, whichever is appropriate. E.g.: >> >> typedef long pgtype_int8[2]; >> typedef long pgtype_int28[4]; >> typedef octet pgtype_macaddr[6]; >> typedef octet pgtype_filename[256]; I think I meant big-endian (that *is* "network order", isn't it? I always forget). Anyway, you get the point. >P.S. Would it be possible to make a pgsql/src/corba module and let me check >this IDL file into it? That way I don't have to keep reposting it. Well, until it's fairly stable, keep reposting it. That way people don't have to keep checking for changes in the tree. -Michael Robinson