Re: BUG #6281: need to remove - Mailing list pgsql-bugs

PostgreSQL 8.4.1 Documentation



Prev

Fast Backward


Fast Forward

Next


----------------------------------------------------------------------------
----


Appendix D. SQL Conformance

Table of ContentsD.1. Supported FeaturesD.2. Unsupported Features
 This section attempts to outline to what extent PostgreSQL conforms to the
current SQL standard. The following information is not a full statement of
conformance, but it presents the main topics in as much detail as is both
reasonable and useful for users.

The formal name of the SQL standard is ISO/IEC 9075 "Database Language SQL".
A revised version of the standard is released from time to time; the most
recent update appearing in 2008. The 2008 version is referred to as ISO/IEC
9075:2008, or simply as SQL:2008. The versions prior to that were SQL:2003,
SQL:1999, and SQL-92. Each version replaces the previous one, so claims of
conformance to earlier versions have no official merit. PostgreSQL
development aims for conformance with the latest official version of the
standard where such conformance does not contradict traditional features or
common sense. The PostgreSQL project is not represented in the ISO/IEC 9075
Working Group during the preparation of the SQL standard releases, but even
so, many of the features required by the SQL standard are supported, though
sometimes with slightly differing syntax or function. Further moves towards
conformance can be expected over time.

SQL-92 defined three feature sets for conformance: Entry, Intermediate, and
Full. Most database management systems claiming SQL standard conformance
were conforming at only the Entry level, since the entire set of features in
the Intermediate and Full levels was either too voluminous or in conflict
with legacy behaviors.

Starting with SQL:1999, the SQL standard defines a large set of individual
features rather than the ineffectively broad three levels found in SQL-92. A
large subset of these features represents the "Core" features, which every
conforming SQL implementation must supply. The rest of the features are
purely optional. Some optional features are grouped together to form
"packages", which SQL implementations can claim conformance to, thus
claiming conformance to particular groups of features.

The SQL:2008 and SQL:2003 standard versions are also split into a number of
parts. Each is known by a shorthand name. Note that these parts are not
consecutively numbered.


.
ISO/IEC 9075-1 Framework (SQL/Framework)

.
ISO/IEC 9075-2 Foundation (SQL/Foundation)

.
ISO/IEC 9075-3 Call Level Interface (SQL/CLI)

.
ISO/IEC 9075-4 Persistent Stored Modules (SQL/PSM)

.
ISO/IEC 9075-9 Management of External Data (SQL/MED)

.
ISO/IEC 9075-10 Object Language Bindings (SQL/OLB)

.
ISO/IEC 9075-11 Information and Definition Schemas (SQL/Schemata)

.
ISO/IEC 9075-13 Routines and Types using the Java Language (SQL/JRT)

.
ISO/IEC 9075-14 XML-related specifications (SQL/XML)




 The PostgreSQL core covers parts 1, 2, 9, 11, and 14. Part 3 is covered by
the ODBC driver, and part 13 is covered by the PL/Java plug-in, but exact
conformance is currently not being verified for these components. There are
currently no implementations of parts 4 and 10 for PostgreSQL.

PostgreSQL supports most of the major features of SQL:2008. Out of 179
mandatory features required for full Core conformance, PostgreSQL conforms
to at least 160. In addition, there is a long list of supported optional
features. It might be worth noting that at the time of writing, no current
version of any database management system claims full conformance to Core
SQL:2008.

In the following two sections, we provide a list of those features that
PostgreSQL supports, followed by a list of the features defined in SQL:2008
which are not yet supported in PostgreSQL. Both of these lists are
approximate: There might be minor details that are nonconforming for a
feature that is listed as supported, and large parts of an unsupported
feature might in fact be implemented. The main body of the documentation
always contains the most accurate information about what does and does not
work.




Note: Feature codes containing a hyphen are subfeatures. Therefore, if a
particular subfeature is not supported, the main feature is listed as
unsupported even if some other subfeatures are supported.


----------------------------------------------------------------------------
----



Prev

Home

Next



SQL Key Words

Up


Thanks
Jim Jackson
Realtor
Regional Sales Manager
Century 21 Judge Fite Company
Arlington Regional Office
(817) 804-3282 Office
(817) 233-2385 Cell


-----Original Message-----
From: Kevin Grittner [mailto:Kevin.Grittner@wicourts.gov]
Sent: Friday, November 04, 2011 3:19 PM
To: Jim Jackson (817) 233-2385
Cc: pgsql-bugs@postgresql.org; 'Craig Ringer'
Subject: RE: [BUGS] BUG #6281: need to remove

"Jim Jackson (817) 233-2385" <jimjackson@judgefite.com> wrote:

> The postgreSQL was a separate installation step that had to be
> done separately from the poker software load to support the poker
> software.

The question is, where did you get the installation software for
that step?  If you got it from the poker software provider, it is
probably something nobody on this list has ever seen.  We would like
to help you if we could, but it doesn't sound like it is our
software causing you the problems.  When you download software from
somewhere, the download source is where you should go with problems
with it.  We have no special knowledge of what their installer does.

I see that while I've been typing this you asked whether
re-installing would help.  Again, if it's not an installer we've
seen, so we don't know.  The right people to be asking are the
people you got it from.

-Kevin