From: Michael Robinson <robinson@public.bta.net.cn>
To: pgsql-interfaces@hub.org
To: taral@cyberjunkie.com
Subject: Re: [INTERFACES] Updated IDL with considerations for COSS
Date: Mon, 16 Nov 1998 23:31:03 +0800 (GMT)
Message-ID: <199811161531.XAA09964@public.bta.net.cn> (raw)
"Taral" <taral@cyberjunkie.com> writes:
>module PostgreSQL {
In the interest of maximum interoperability, I'd suggest finding what is
the predominant deployed CORBA database interface (or interfaces), factoring
out the commonalities, differences, and incompatibilities with what we want
to do with PostgreSQL, and see if we can benefit from interface inheritance
(single or multiple).
> // Standard types
> typedef short int2type;
> typedef long int4type;
In the future, we will want to implement an Interface Repository to map
the PostgreSQL type tables to CORBA IDL. Since that involves an indeterminate
number of user-defined types, I recommend carving out namespace for that
purpose at the beginning, e.g.:
typedef short pgtype_int2;
typedef long pgtype_int4;
> struct int8type {
> long lsw;
> long msw;
> };
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];
Etc. It's more orthogonal that way. But again, if prevailing practice is
something else, we should look closely at that. Sign extension of multi-
long integral types is another problem that someone has presumably already
solved for us.
-Michael Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: robinson@public.bta.net.cn, pgsql-interfaces@hub.org, taral@cyberjunkie.com
Subject: Re: [INTERFACES] Updated IDL with considerations for COSS
In-Reply-To: <199811161531.XAA09964@public.bta.net.cn>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox