bear some similarity to PL/Java and PL/J.
I think the big question is whether we are ever going to implement
these? I think we need to decide that before I mention them.
The SQL/Schemata thing is already in. I think we should at least
mention which features that we already have are from what
On Sat, Aug 26, 2006 at 08:38:43PM +0200, Peter Eisentraut wrote:
> David Fetter wrote:
> > We claim SQL standard compliance,
>
> No, we don't. And SQL conformance doesn't require you to implement
> all parts anyway.
Right. It'd be nice to be able to tell what level of conformance we
have to wh
Peter Eisentraut wrote:
David Fetter wrote:
We claim SQL standard compliance,
No, we don't. And SQL conformance doesn't require you to implement all
parts anyway.
so since those are part of
SQL:2003, we probably ought to mention them. SQL/PSM is a
programming language that lives inside
David Fetter wrote:
> The SQL/Schemata thing is already in. I think we should at least
> mention which features that we already have are from what part of the
> standard.
We do. Read the documentation.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(en
Bruce Momjian wrote:
> I made it clear in the section that the XML syntax was being checked,
> not validation against a schema. You want Check and Validation
> sections?
"Valid" and "well-formed" have very specific distinct meanings in XML.
(Note that "check" doesn't have any meaning there.) W
David Fetter wrote:
> We claim SQL standard compliance,
No, we don't. And SQL conformance doesn't require you to implement all
parts anyway.
> so since those are part of
> SQL:2003, we probably ought to mention them. SQL/PSM is a
> programming language that lives inside the database, and DB2
David Fetter wrote:
> > > mention which features that we already have are from what part of
> > > the standard. As far as the rest of the standard goes, we might
> > > want to mention whether we've even considered any of each piece in
> > > the TODO list, and what sub-pieces, if any, are already
>
On Sat, Aug 26, 2006 at 01:16:06PM -0400, Bruce Momjian wrote:
> David Fetter wrote:
> > On Sat, Aug 26, 2006 at 12:48:32PM -0400, Bruce Momjian wrote:
> > > David Fetter wrote:
> > > > On Fri, Aug 25, 2006 at 08:37:19PM -0400, Bruce Momjian wrote:
> >
> > > > > > Speaking of other parts of the SQ
David Fetter wrote:
> On Sat, Aug 26, 2006 at 12:48:32PM -0400, Bruce Momjian wrote:
> > David Fetter wrote:
> > > On Fri, Aug 25, 2006 at 08:37:19PM -0400, Bruce Momjian wrote:
>
> > > > > Speaking of other parts of the SQL:2003 standard, how about one
> > > > > section each that mentions them?
On Sat, Aug 26, 2006 at 12:48:32PM -0400, Bruce Momjian wrote:
> David Fetter wrote:
> > On Fri, Aug 25, 2006 at 08:37:19PM -0400, Bruce Momjian wrote:
> > > > Speaking of other parts of the SQL:2003 standard, how about one
> > > > section each that mentions them? There's
> > > >
> > > > Part 4:
David Fetter wrote:
> On Fri, Aug 25, 2006 at 08:37:19PM -0400, Bruce Momjian wrote:
> > David Fetter wrote:
> > > On Fri, Aug 25, 2006 at 07:46:57PM -0400, Bruce Momjian wrote:
> > > > Here is an new XML section for our SGML documentation. It
> > > > explains the various XML capabilities, if we s
Magnus Hagander wrote:
> > Indexing
> >
> > Because XML documents are stored as text, full-text indexing tool
> > /contrib/tsearch2 can be used to index XML documents. Of
> > course, the searches are text searches, with no XML
> > awareness, but tsearch2 can be used with other XML
> >
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > XML Document Support
> >
> > XML support is not one capability, but a variety of features
> > supported by a database.
>
> database system
Done.
> > Storage
> > ---
> > PostgreSQL stores XML documents as ordinary text do
On Fri, Aug 25, 2006 at 08:37:19PM -0400, Bruce Momjian wrote:
> David Fetter wrote:
> > On Fri, Aug 25, 2006 at 07:46:57PM -0400, Bruce Momjian wrote:
> > > Here is an new XML section for our SGML documentation. It
> > > explains the various XML capabilities, if we support them, and
> > > how to
14 matches
Mail list logo