From: Josh Berkus <josh@agliodbs.com>
To: Joe Conway <mail@joeconway.com>
Cc: pgsql-advocacy@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: SQL Spec Compliance Questions
Date: Fri, 2 Apr 2004 08:53:04 -0800
Message-ID: <200404020853.04880.josh@agliodbs.com> (raw)
In-Reply-To: <406D9943.8070401@joeconway.com>
References: <200403302050.12415.josh@agliodbs.com>
<200404020838.22698.josh@agliodbs.com>
<406D9943.8070401@joeconway.com>
Joe,
> After re-reading it, I think it is related to (or at least similar to)
> the work Tom is currently doing to allow composite types as table
> attributes.
That's what I thought at first as well, and told the requestor that we would
support them in the next two versions. But reading that paragraph makes me
think that the type is somehow supposed to contain metadata or summary data
for the table itself.
--
Josh Berkus
Aglio Database Solutions
San Francisco
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-sql@postgresql.org
Cc: josh@agliodbs.com, mail@joeconway.com, pgsql-advocacy@postgresql.org
Subject: Re: SQL Spec Compliance Questions
In-Reply-To: <200404020853.04880.josh@agliodbs.com>
* 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