Skip to content

P
Postgres FD Implementation
Commit 090dd22d authored by Thomas G. Lockhart's avatar Thomas G. Lockhart
Browse files
Options

Implement SQL99 OVERLAY(). Allows substitution of a substring in a string. 

Implement SQL99 SIMILAR TO as a synonym for our existing operator "~".
Implement SQL99 regular expression SUBSTRING(string FROM pat FOR escape).
 Extend the definition to make the FOR clause optional.
 Define textregexsubstr() to actually implement this feature.
Update the regression test to include these new string features.
 All tests pass.
Rename the regular expression support routines from "pg95_xxx" to "pg_xxx".
Define CREATE CHARACTER SET in the parser per SQL99. No implementation yet.
parent 469cb65a
Hide whitespace changes
Inline Side-by-side
Showing with 1800 additions and 1692 deletions
doc/src/sgml/advanced.sgml
View file @ 090dd22d
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.27 2002/02/12 22:25:15 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.28 2002/06/11 15:32:32 thomas Exp $
--> -->
<chapter id="tutorial-advanced"> <chapter id="tutorial-advanced">
...@@ -46,14 +46,14 @@ $Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.27 2002/02/12 22:25:15 mo ...@@ -46,14 +46,14 @@ $Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.27 2002/02/12 22:25:15 mo
<firstterm>view</firstterm> over the query, which gives a name to <firstterm>view</firstterm> over the query, which gives a name to
the query that you can refer to like an ordinary table. the query that you can refer to like an ordinary table.
<programlisting> <programlisting>
CREATE VIEW myview AS CREATE VIEW myview AS
SELECT city, temp_lo, temp_hi, prcp, date, location SELECT city, temp_lo, temp_hi, prcp, date, location
FROM weather, cities FROM weather, cities
WHERE city = name; WHERE city = name;
SELECT * FROM myview; SELECT * FROM myview;
</programlisting> </programlisting>
</para> </para>
<para> <para>
...@@ -101,32 +101,30 @@ SELECT * FROM myview; ...@@ -101,32 +101,30 @@ SELECT * FROM myview;
<para> <para>
The new declaration of the tables would look like this: The new declaration of the tables would look like this:
<programlisting> <programlisting>
CREATE TABLE cities ( CREATE TABLE cities (
city varchar(80) primary key, city varchar(80) primary key,
location point location point
); );
CREATE TABLE weather ( CREATE TABLE weather (
city varchar(80) references cities, city varchar(80) references cities,
temp_lo int, temp_lo int,
temp_hi int, temp_hi int,
prcp real, prcp real,
date date date date
); );
</programlisting>
</programlisting>
Now try inserting an invalid record: Now try inserting an invalid record:
<programlisting> <programlisting>
INSERT INTO weather VALUES ('Berkeley', 45, 53, 0.0, '1994-11-28'); INSERT INTO weather VALUES ('Berkeley', 45, 53, 0.0, '1994-11-28');
</programlisting> </programlisting>
<screen> <screen>
ERROR: &lt;unnamed&gt; referential integrity violation - key referenced from weather not found in cities ERROR: &lt;unnamed&gt; referential integrity violation - key referenced from weather not found in cities
</screen> </screen>
</para> </para>
<para> <para>
...@@ -162,7 +160,8 @@ ERROR: &lt;unnamed&gt; referential integrity violation - key referenced from we ...@@ -162,7 +160,8 @@ ERROR: &lt;unnamed&gt; referential integrity violation - key referenced from we
Suppose that we want to record a payment of $100.00 from Alice's account Suppose that we want to record a payment of $100.00 from Alice's account
to Bob's account. Simplifying outrageously, the SQL commands for this to Bob's account. Simplifying outrageously, the SQL commands for this
might look like might look like
<programlisting>
<programlisting>
UPDATE accounts SET balance = balance - 100.00 UPDATE accounts SET balance = balance - 100.00
WHERE name = 'Alice'; WHERE name = 'Alice';
UPDATE branches SET balance = balance - 100.00 UPDATE branches SET balance = balance - 100.00
...@@ -171,7 +170,10 @@ UPDATE accounts SET balance = balance + 100.00 ...@@ -171,7 +170,10 @@ UPDATE accounts SET balance = balance + 100.00
WHERE name = 'Bob'; WHERE name = 'Bob';
UPDATE branches SET balance = balance + 100.00 UPDATE branches SET balance = balance + 100.00
WHERE name = (SELECT branch_name FROM accounts WHERE name = 'Bob'); WHERE name = (SELECT branch_name FROM accounts WHERE name = 'Bob');
</programlisting> </programlisting>
</para>
<para>
The details of these commands are not important here; the important The details of these commands are not important here; the important
point is that there are several separate updates involved to accomplish point is that there are several separate updates involved to accomplish
this rather simple operation. Our bank's officers will want to be this rather simple operation. Our bank's officers will want to be
...@@ -219,13 +221,17 @@ UPDATE branches SET balance = balance + 100.00 ...@@ -219,13 +221,17 @@ UPDATE branches SET balance = balance + 100.00
the SQL commands of the transaction with the SQL commands of the transaction with
<command>BEGIN</> and <command>COMMIT</> commands. So our banking <command>BEGIN</> and <command>COMMIT</> commands. So our banking
transaction would actually look like transaction would actually look like
<programlisting>
<programlisting>
BEGIN; BEGIN;
UPDATE accounts SET balance = balance - 100.00 UPDATE accounts SET balance = balance - 100.00
WHERE name = 'Alice'; WHERE name = 'Alice';
-- etc etc -- etc etc
COMMIT; COMMIT;
</programlisting> </programlisting>
</para>
<para>
If, partway through the transaction, we decide we don't want to If, partway through the transaction, we decide we don't want to
commit (perhaps we just noticed that Alice's balance went negative), commit (perhaps we just noticed that Alice's balance went negative),
we can issue the command <command>ROLLBACK</> instead of we can issue the command <command>ROLLBACK</> instead of
...@@ -272,25 +278,25 @@ COMMIT; ...@@ -272,25 +278,25 @@ COMMIT;
implicitly when you list all cities. If you're really clever you implicitly when you list all cities. If you're really clever you
might invent some scheme like this: might invent some scheme like this:
<programlisting> <programlisting>
CREATE TABLE capitals ( CREATE TABLE capitals (
name text, name text,
population real, population real,
altitude int, -- (in ft) altitude int, -- (in ft)
state char(2) state char(2)
); );
CREATE TABLE non_capitals ( CREATE TABLE non_capitals (
name text, name text,
population real, population real,
altitude int -- (in ft) altitude int -- (in ft)
); );
CREATE VIEW cities AS CREATE VIEW cities AS
SELECT name, population, altitude FROM capitals SELECT name, population, altitude FROM capitals
UNION UNION
SELECT name, population, altitude FROM non_capitals; SELECT name, population, altitude FROM non_capitals;
</programlisting> </programlisting>
This works OK as far as querying goes, but it gets ugly when you This works OK as far as querying goes, but it gets ugly when you
need to update several rows, to name one thing. need to update several rows, to name one thing.
...@@ -299,18 +305,20 @@ CREATE VIEW cities AS ...@@ -299,18 +305,20 @@ CREATE VIEW cities AS
<para> <para>
A better solution is this: A better solution is this:
<programlisting> <programlisting>
CREATE TABLE cities ( CREATE TABLE cities (
name text, name text,
population real, population real,
altitude int -- (in ft) altitude int -- (in ft)
); );
CREATE TABLE capitals ( CREATE TABLE capitals (
state char(2) state char(2)
) INHERITS (cities); ) INHERITS (cities);
</programlisting> </programlisting>
</para>
<para>
In this case, a row of <classname>capitals</classname> In this case, a row of <classname>capitals</classname>
<firstterm>inherits</firstterm> all columns (<structfield>name</>, <firstterm>inherits</firstterm> all columns (<structfield>name</>,
<structfield>population</>, and <structfield>altitude</>) from its <structfield>population</>, and <structfield>altitude</>) from its
...@@ -328,22 +336,22 @@ CREATE TABLE capitals ( ...@@ -328,22 +336,22 @@ CREATE TABLE capitals (
including state capitals, that are located at an altitude including state capitals, that are located at an altitude
over 500 ft.: over 500 ft.:
<programlisting> <programlisting>
SELECT name, altitude SELECT name, altitude
FROM cities FROM cities
WHERE altitude &gt; 500; WHERE altitude &gt; 500;
</programlisting> </programlisting>
which returns: which returns:
<screen> <screen>
name | altitude name | altitude
-----------+---------- -----------+----------
Las Vegas | 2174 Las Vegas | 2174
Mariposa | 1953 Mariposa | 1953
Madison | 845 Madison | 845
(3 rows) (3 rows)
</screen> </screen>
</para> </para>
<para> <para>
...@@ -351,11 +359,11 @@ SELECT name, altitude ...@@ -351,11 +359,11 @@ SELECT name, altitude
all the cities that are not state capitals and all the cities that are not state capitals and
are situated at an altitude of 500 ft. or higher: are situated at an altitude of 500 ft. or higher:
<programlisting> <programlisting>
SELECT name, altitude SELECT name, altitude
FROM ONLY cities FROM ONLY cities
WHERE altitude &gt; 500; WHERE altitude &gt; 500;
</programlisting> </programlisting>
<screen> <screen>
name | altitude name | altitude
...@@ -363,7 +371,7 @@ SELECT name, altitude ...@@ -363,7 +371,7 @@ SELECT name, altitude
Las Vegas | 2174 Las Vegas | 2174
Mariposa | 1953 Mariposa | 1953
(2 rows) (2 rows)
</screen> </screen>
</para> </para>
<para> <para>
...@@ -397,7 +405,6 @@ SELECT name, altitude ...@@ -397,7 +405,6 @@ SELECT name, altitude
site</ulink> for links to more resources. site</ulink> for links to more resources.
</para> </para>
</sect1> </sect1>
</chapter> </chapter>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
......
doc/src/sgml/datatype.sgml
View file @ 090dd22d
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.92 2002/05/03 04:11:07 tgl Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.93 2002/06/11 15:32:32 thomas Exp $
--> -->
<chapter id="datatype"> <chapter id="datatype">
...@@ -2637,7 +2637,8 @@ SELECT * FROM test1 WHERE a; ...@@ -2637,7 +2637,8 @@ SELECT * FROM test1 WHERE a;
The <type>inet</type> type holds an IP host address, and The <type>inet</type> type holds an IP host address, and
optionally the identity of the subnet it is in, all in one field. optionally the identity of the subnet it is in, all in one field.
The subnet identity is represented by the number of bits in the The subnet identity is represented by the number of bits in the
network part of the address (the <quote>netmask</quote>). If the netmask is 32, network part of the address (the <quote>netmask</quote>). If the
netmask is 32,
then the value does not indicate a subnet, only a single host. then the value does not indicate a subnet, only a single host.
Note that if you want to accept networks only, you should use the Note that if you want to accept networks only, you should use the
<type>cidr</type> type rather than <type>inet</type>. <type>cidr</type> type rather than <type>inet</type>.
......
doc/src/sgml/func.sgml
View file @ 090dd22d
This source diff could not be displayed because it is too large. You can view the blob instead.
doc/src/sgml/release.sgml
View file @ 090dd22d
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.138 2002/05/22 17:20:58 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.139 2002/06/11 15:32:33 thomas Exp $
--> -->
<appendix id="release"> <appendix id="release">
...@@ -44,6 +44,9 @@ Access privileges on procedural languages ...@@ -44,6 +44,9 @@ Access privileges on procedural languages
CREATE DATABASE has OWNER option so superuser can create DB for someone else CREATE DATABASE has OWNER option so superuser can create DB for someone else
Kerberos 5 support now works with Heimdal Kerberos 5 support now works with Heimdal
Database and user-specific session defaults for run-time configuration variables (ALTER DATABASE ... SET and ALTER USER ... SET) Database and user-specific session defaults for run-time configuration variables (ALTER DATABASE ... SET and ALTER USER ... SET)
String function OVERLAY() implemented per SQL99
Regular expression operator SIMILAR TO implemented per SQL99
Regular expression function SUBSTRING() implemented per SQL99
]]></literallayout> ]]></literallayout>
</sect1> </sect1>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment