|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.186 2007/01/25 11:53:50 petere Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.187 2007/01/29 13:24:30 petere Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="datatype"> |
4 | 4 | <title id="datatype-title">Data Types</title> |
@@ -3538,86 +3538,6 @@ SET xmloption TO { DOCUMENT | CONTENT }; |
3538 | 3538 | processed in UTF-8, computations will be most efficient if the |
3539 | 3539 | server encoding is also UTF-8. |
3540 | 3540 | </para> |
3541 | | - |
3542 | | - <para> |
3543 | | - <acronym>XML</> (Extensible Markup Language) support is not |
3544 | | - just the existance of an <type>xml</type> data type, but a |
3545 | | - variety of features supported by a database system. These |
3546 | | - capabilities include import/export, indexing, searching, |
3547 | | - transforming, and <acronym>XML</> to <acronym>SQL</> mapping. |
3548 | | - <productname>PostgreSQL</> supports some but not all of these |
3549 | | - <acronym>XML</> capabilities. For an overview of <acronym>XML</> |
3550 | | - use in databases, see <ulink |
3551 | | - url="http://www.rpbourret.com/xml/XMLAndDatabases.htm"></>. |
3552 | | - </para> |
3553 | | - |
3554 | | - <variablelist> |
3555 | | - <varlistentry> |
3556 | | - <term>Import/Export</term> |
3557 | | - <listitem> |
3558 | | - |
3559 | | - <para> |
3560 | | - There is no facility for mapping <acronym>XML</> to relational |
3561 | | - tables. An external tool must be used for this. One simple way to |
3562 | | - export <acronym>XML</> is to use <application>psql</> in |
3563 | | - <acronym>HTML</> mode (<literal>\pset format html</>), and convert |
3564 | | - the <acronym>XHTML</> output to XML using an external tool. |
3565 | | - </para> |
3566 | | - </listitem> |
3567 | | - </varlistentry> |
3568 | | - |
3569 | | - <varlistentry> |
3570 | | - <term>Indexing</term> |
3571 | | - <listitem> |
3572 | | - |
3573 | | - <para> |
3574 | | - <filename>/contrib/xml2</> functions can be used in expression |
3575 | | - indexes to index specific <acronym>XML</> fields. To index the |
3576 | | - full contents of <acronym>XML</> documents, the full-text indexing |
3577 | | - tool <filename>/contrib/tsearch2</> can be used. Of course, |
3578 | | - Tsearch2 indexes have no <acronym>XML</> awareness so additional |
3579 | | - <filename>/contrib/xml2</> checks should be added to queries. |
3580 | | - </para> |
3581 | | - </listitem> |
3582 | | - </varlistentry> |
3583 | | - |
3584 | | - <varlistentry> |
3585 | | - <term>Searching</term> |
3586 | | - <listitem> |
3587 | | - |
3588 | | - <para> |
3589 | | - XPath searches are implemented using <filename>/contrib/xml2</>. |
3590 | | - It processes <acronym>XML</> text documents and returns results |
3591 | | - based on the requested query. |
3592 | | - </para> |
3593 | | - </listitem> |
3594 | | - </varlistentry> |
3595 | | - |
3596 | | - <varlistentry> |
3597 | | - <term>Transforming</term> |
3598 | | - <listitem> |
3599 | | - |
3600 | | - <para> |
3601 | | - <filename>/contrib/xml2</> supports <acronym>XSLT</> (Extensible |
3602 | | - Stylesheet Language Transformation). |
3603 | | - </para> |
3604 | | - </listitem> |
3605 | | - </varlistentry> |
3606 | | - |
3607 | | - <varlistentry> |
3608 | | - <term>XML to SQL Mapping</term> |
3609 | | - <listitem> |
3610 | | - |
3611 | | - <para> |
3612 | | - This involves converting <acronym>XML</> data to and from |
3613 | | - relational structures. <productname>PostgreSQL</> has no internal |
3614 | | - support for such mapping, and relies on external tools to do such |
3615 | | - conversions. |
3616 | | - </para> |
3617 | | - </listitem> |
3618 | | - </varlistentry> |
3619 | | - </variablelist> |
3620 | | - |
3621 | 3541 | </sect1> |
3622 | 3542 |
|
3623 | 3543 | </chapter> |