Project

General

Profile

« Previous | Next » 

Revision 12539

Added by Aaron Marcuse-Kubitza almost 11 years ago

web/links/index.htm: updated to Firefox bookmarks: PostgreSQL: added links for error reporting levels and how to hide stack traces in psql. SQL: added links for recursive queries, which can be used to traverse hierarchical (parent-pointer) tables.

View differences:

index.htm
34 34 
        <DT><A HREF="https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegCore" name="__https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegCore" ADD_DATE="1354727779" ICON_URI="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1347421715"><img width="16" height="16" src="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1347421715" style="margin-right: 0.5em;"/>VegCore</A><a name="__VegCore" href="#__VegCore" style="margin-left: 0.5em;">&para;</a>
35 35 
        <DT><A HREF="https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegBIEN_schema" name="__https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegBIEN_schema" ADD_DATE="1344469303" ICON_URI="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242"><img width="16" height="16" src="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242" style="margin-right: 0.5em;"/>VegBIEN</A><a name="__VegBIEN" href="#__VegBIEN" style="margin-left: 0.5em;">&para;</a>
36 36 
        <DT><A HREF="https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegBIEN_FAQ" name="__https://projects.nceas.ucsb.edu/nceas/projects/bien/wiki/VegBIEN_FAQ" ADD_DATE="1389803305" ICON_URI="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242" LAST_CHARSET="UTF-8"><img width="16" height="16" src="https://projects.nceas.ucsb.edu/nceas/favicon.ico?1391043242" style="margin-right: 0.5em;"/>FAQ</A><a name="__FAQ" href="#__FAQ" style="margin-left: 0.5em;">&para;</a>
37 
        <DT><A HREF="http://vegbiendev.nceas.ucsb.edu/phppgadmin/redirect.php?subject=schema&server=localhost%3A5432%3Aallow&database=vegbien&schema=public" name="__http://vegbiendev.nceas.ucsb.edu/phppgadmin/redirect.php?subject=schema&server=localhost%3A5432%3Aallow&database=vegbien&schema=public" ADD_DATE="1362008923" ICON_URI="http://vegbiendev.nceas.ucsb.edu/phppgadmin/images/themes/default/Introduction.png" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://vegbiendev.nceas.ucsb.edu/phppgadmin/images/themes/default/Introduction.png" style="margin-right: 0.5em;"/>vegbiendev</A><a name="__vegbiendev" href="#__vegbiendev" style="margin-left: 0.5em;">&para;</a>
37 
        <DT><A HREF="http://vegbiendev.nceas.ucsb.edu/phppgadmin/redirect.php?server=localhost%3A5432%3Aallow&subject=database&database=vegbien" name="__http://vegbiendev.nceas.ucsb.edu/phppgadmin/redirect.php?server=localhost%3A5432%3Aallow&subject=database&database=vegbien" ADD_DATE="1362008923" ICON_URI="http://vegbiendev.nceas.ucsb.edu/phppgadmin/images/themes/default/Introduction.png"><img width="16" height="16" src="http://vegbiendev.nceas.ucsb.edu/phppgadmin/images/themes/default/Introduction.png" style="margin-right: 0.5em;"/>vegbiendev</A><a name="__vegbiendev" href="#__vegbiendev" style="margin-left: 0.5em;">&para;</a>
38 38 
        <DT><A HREF="http://vegbiendev.nceas.ucsb.edu/phpmyadmin/" name="__http://vegbiendev.nceas.ucsb.edu/phpmyadmin/" ADD_DATE="1361027615" ICON_URI="http://vegbiendev.nceas.ucsb.edu/phpmyadmin/favicon.ico"><img width="16" height="16" src="http://vegbiendev.nceas.ucsb.edu/phpmyadmin/favicon.ico" style="margin-right: 0.5em;"/>&quot;</A><a name="__&quot;" href="#__&quot;" style="margin-left: 0.5em;">&para;</a>
39 39 
        <DT><A HREF="http://nimoy.nceas.ucsb.edu/phpmyadmin/" name="__http://nimoy.nceas.ucsb.edu/phpmyadmin/" ADD_DATE="1318544417" ICON_URI="http://nimoy.nceas.ucsb.edu/phpmyadmin/favicon.ico"><img width="16" height="16" src="http://nimoy.nceas.ucsb.edu/phpmyadmin/favicon.ico" style="margin-right: 0.5em;"/>nimoy</A><a name="__nimoy" href="#__nimoy" style="margin-left: 0.5em;">&para;</a>
40 40 
        <DT><A HREF="http://starscream.nceas.ucsb.edu/~aaronmk/phppgadmin/redirect.php?subject=schema&server=%3A5432%3Aallow&database=vegbien&schema=public&" name="__http://starscream.nceas.ucsb.edu/~aaronmk/phppgadmin/redirect.php?subject=schema&server=%3A5432%3Aallow&database=vegbien&schema=public&" ADD_DATE="1362008964" ICON_URI="http://starscream.nceas.ucsb.edu/~aaronmk/phppgadmin/images/themes/default/Introduction.png"><img width="16" height="16" src="http://starscream.nceas.ucsb.edu/~aaronmk/phppgadmin/images/themes/default/Introduction.png" style="margin-right: 0.5em;"/>starscream</A><a name="__starscream" href="#__starscream" style="margin-left: 0.5em;">&para;</a>
......
832 832 
                          text_var3 = PG_EXCEPTION_HINT;
833 833 
&quot;
834 834 
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/sql-createdomain.html" name="http://www.postgresql.org/docs/9.3/static/sql-createdomain.html" ADD_DATE="1386257057" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: CREATE DOMAIN</A><a name="PostgreSQL: Documentation: 9.3: CREATE DOMAIN" href="#PostgreSQL: Documentation: 9.3: CREATE DOMAIN" style="margin-left: 0.5em;">&para;</a>
835 
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/sql-createview.html" name="http://www.postgresql.org/docs/9.3/static/sql-createview.html" ADD_DATE="1393552021" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: CREATE VIEW</A><a name="PostgreSQL: Documentation: 9.3: CREATE VIEW" href="#PostgreSQL: Documentation: 9.3: CREATE VIEW" style="margin-left: 0.5em;">&para;</a>
836 
<DD>&quot;Simple views are automatically updatable: the system will allow INSERT, UPDATE and DELETE statements to be used on the view in the same way as on a regular table.&quot; (this is only available in 9.3+)
835 837 
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/runtime-config-logging.html#GUC-LOG-ERROR-VERBOSITY" name="http://www.postgresql.org/docs/9.3/static/runtime-config-logging.html#GUC-LOG-ERROR-VERBOSITY" ADD_DATE="1384823719" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: Error Reporting and Logging</A><a name="PostgreSQL: Documentation: 9.3: Error Reporting and Logging" href="#PostgreSQL: Documentation: 9.3: Error Reporting and Logging" style="margin-left: 0.5em;">&para;</a>
836 
<DD>page's description: &#39;Valid values are TERSE, DEFAULT, and VERBOSE, each adding more fields to displayed messages. TERSE excludes the logging of DETAIL, HINT, QUERY, and CONTEXT error information. VERBOSE output includes the SQLSTATE error code (see also Appendix A) and the source code file name, function name, and line number that generated the error. Only superusers can change this setting [but it also exists in psql].&#39;
838 
<DD>&quot;Valid values are TERSE, DEFAULT, and VERBOSE, each adding more fields to displayed messages. TERSE excludes the logging of DETAIL, HINT, QUERY, and CONTEXT error information. VERBOSE output includes the SQLSTATE error code (see also Appendix A) and the source code file name, function name, and line number that generated the error. Only superusers can change this setting [but it also exists in psql].&quot;
839 

  		




  
  840
  
    
to hide stack traces in psql:


  		




  
  841
  
    
\set VERBOSITY terse


  		




  
  842
  
    

  		




  
  843
  
    
there is unfortunately *no* option to do this in pgAdmin


  		




  
  844
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHEN" name="http://www.postgresql.org/docs/9.3/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHEN" ADD_DATE="1393518205" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: Error Reporting and Logging: 18.8.2. When To Log</A><a name="PostgreSQL: Documentation: 9.3: Error Reporting and Logging: 18.8.2. When To Log" href="#PostgreSQL: Documentation: 9.3: Error Reporting and Logging: 18.8.2. When To Log" style="margin-left: 0.5em;">&para;</a>


  		




  
  845
  
    
<DD>&quot;client_min_messages [...] Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, LOG, NOTICE, WARNING, ERROR, FATAL, and PANIC. Each level includes all the levels that follow it.&quot;


  		




  837
  846
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/interactive/xfunc-volatility.html" name="http://www.postgresql.org/docs/9.3/interactive/xfunc-volatility.html" ADD_DATE="1393355422" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: Function Volatility Categories **</A><a name="PostgreSQL: Documentation: 9.3: Function Volatility Categories **" href="#PostgreSQL: Documentation: 9.3: Function Volatility Categories **" style="margin-left: 0.5em;">&para;</a>


  		




  838
  847
  
    
<DD>-


  		




  839
  848
  
    
*** &quot;A common error is to label a function IMMUTABLE when its results depend on a configuration parameter. For example, a function that manipulates timestamps might well have results that depend on the TimeZone setting. For safety, such functions should be labeled STABLE instead.&quot;


  		




  840
  
  
    
this especially includes functions that depend on the search_path! (ie. that lack schema qualifiers on all invoked functions.) however, this effect will only be noticeable if the function is called on only *constant* values in a *PL/pgSQL* function, in which case the wrong search_path (the one in effect at *create* time) will be used.


  		




  
  849
  
    
this especially includes functions that depend on the search_path! (ie. that don&#39;t have schema qualifiers on all invoked functions.) however, this effect will only be noticeable if the function is called on only *constant* values in a *PL/pgSQL* function, in which case the wrong search_path (the one in effect at *create* time) will be used.


  		




  841
  850
  
    

  		




  842
  851
  
    
** &quot;There is relatively little difference between STABLE and IMMUTABLE categories when considering simple interactive queries that are planned and immediately executed: it doesn&#39;t matter a lot whether a function is executed once during planning or once during query execution startup. But there is a big difference if the plan is saved and reused later. Labeling a function IMMUTABLE when it really isn&#39;t might allow it to be prematurely folded to a constant during planning, resulting in a stale value being re-used during subsequent uses of the plan. This is a hazard when using prepared statements or when using function languages that cache plans (such as PL/pgSQL).&quot;


  		




  843
  852
  
    
ie. if you are going to use your STABLE function in a PL/pgSQL function, be sure to label it STABLE so that it does not get constant-folded until call time (if labeled IMMUTABLE, it would be folded right away when the function is created)


  		




  844
  853
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/functions-geometry.html" name="http://www.postgresql.org/docs/9.3/static/functions-geometry.html" ADD_DATE="1393319486" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: Geometric Functions and Operators</A><a name="PostgreSQL: Documentation: 9.3: Geometric Functions and Operators" href="#PostgreSQL: Documentation: 9.3: Geometric Functions and Operators" style="margin-left: 0.5em;">&para;</a>


  		




  
  854
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/functions-matching.html#POSIX-MATCHING-RULES" name="http://www.postgresql.org/docs/9.3/static/functions-matching.html#POSIX-MATCHING-RULES" ADD_DATE="1393381432" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: Pattern Matching: 9.7.3.5. Regular Expression Matching Rules</A><a name="PostgreSQL: Documentation: 9.3: Pattern Matching: 9.7.3.5. Regular Expression Matching Rules" href="#PostgreSQL: Documentation: 9.3: Pattern Matching: 9.7.3.5. Regular Expression Matching Rules" style="margin-left: 0.5em;">&para;</a>


  		




  
  855
  
    
<DD>&quot;If newline-sensitive matching is specified, . and bracket expressions using ^ will never match the newline character (so that matches will never cross newlines unless the RE explicitly arranges it) and ^ and $ will match the empty string after and before a newline respectively&quot;


  		




  
  856
  
    

  		




  
  857
  
    
&quot;non-newline-sensitive matching (default)&quot;


  		




  
  858
  
    

  		




  
  859
  
    
&quot;If partial newline-sensitive matching is specified, this affects . and bracket expressions as with newline-sensitive matching, but not ^ and $.&quot;


  		




  
  860
  
    
this is the (nonintuitive) default in most other regexp implementations


  		




  
  861
  
    

  		




  
  862
  
    
&quot;If inverse partial newline-sensitive matching is specified, this affects ^ and $ as with newline-sensitive matching, but not . and bracket expressions. This isn&#39;t very useful but is provided for symmetry.&quot;


  		




  845
  863
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/app-pgdump.html" name="http://www.postgresql.org/docs/9.3/static/app-pgdump.html" ADD_DATE="1392338412" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: pg_dump</A><a name="PostgreSQL: Documentation: 9.3: pg_dump" href="#PostgreSQL: Documentation: 9.3: pg_dump" style="margin-left: 0.5em;">&para;</a>


  		




  
  864
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/view-pg-settings.html" name="http://www.postgresql.org/docs/9.3/static/view-pg-settings.html" ADD_DATE="1393515328" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: pg_settings</A><a name="PostgreSQL: Documentation: 9.3: pg_settings" href="#PostgreSQL: Documentation: 9.3: pg_settings" style="margin-left: 0.5em;">&para;</a>


  		




  846
  865
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/pgupgrade.html" name="http://www.postgresql.org/docs/9.3/static/pgupgrade.html" ADD_DATE="1384429194" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: pg_upgrade</A><a name="PostgreSQL: Documentation: 9.3: pg_upgrade" href="#PostgreSQL: Documentation: 9.3: pg_upgrade" style="margin-left: 0.5em;">&para;</a>


  		




  847
  866
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/errcodes-appendix.html" name="http://www.postgresql.org/docs/9.3/static/errcodes-appendix.html" ADD_DATE="1392338775" ICON_URI="http://www.postgresql.org/favicon.ico"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: PostgreSQL Error Codes</A><a name="PostgreSQL: Documentation: 9.3: PostgreSQL Error Codes" href="#PostgreSQL: Documentation: 9.3: PostgreSQL Error Codes" style="margin-left: 0.5em;">&para;</a>


  		




  
  867
  
    
<DD>&quot;For some types of errors, the server reports the name of a database object (a table, table column, data type, or constraint) associated with the error; for example, the name of the unique constraint that caused a unique_violation error. Such names are supplied in separate fields of the error report message so that applications need not try to extract them from the possibly-localized human-readable text of the message. As of PostgreSQL 9.3, complete coverage for this feature exists only for errors in SQLSTATE class 23 (integrity constraint violation), but this is likely to be expanded in future.&quot;


  		




  
  868
  
    
this is especially useful for error parsing in column-based import [wiki.vegpath.org/Column-based_import] (and may even have been motivated by it!)


  		




  848
  869
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/app-psql.html#APP-PSQL-PATTERNS" name="http://www.postgresql.org/docs/9.3/static/app-psql.html#APP-PSQL-PATTERNS" ADD_DATE="1392338475" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: psql</A><a name="PostgreSQL: Documentation: 9.3: psql" href="#PostgreSQL: Documentation: 9.3: psql" style="margin-left: 0.5em;">&para;</a>


  		




  
  870
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/ddl-schemas.html" name="http://www.postgresql.org/docs/9.3/static/ddl-schemas.html" ADD_DATE="1393374155" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: Schemas</A><a name="PostgreSQL: Documentation: 9.3: Schemas" href="#PostgreSQL: Documentation: 9.3: Schemas" style="margin-left: 0.5em;">&para;</a>


  		




  
  871
  
    
<DD>&quot;pg_catalog is always effectively part of the search path. If it is not named explicitly in the path then it is implicitly searched before searching the path&#39;s schemas. This ensures that built-in names will always be findable. However, you can explicitly place pg_catalog at the end of your search path if you prefer to have user-defined names override built-in names.&quot;


  		




  849
  872
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/8.4/static/logfile-maintenance.html" name="http://www.postgresql.org/docs/8.4/static/logfile-maintenance.html" ADD_DATE="1333386461" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: Log File Maintenance</A><a name="PostgreSQL: Documentation: Manuals: Log File Maintenance" href="#PostgreSQL: Documentation: Manuals: Log File Maintenance" style="margin-left: 0.5em;">&para;</a>


  		




  850
  873
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.1/interactive/index.html" name="http://www.postgresql.org/docs/9.1/interactive/index.html" ADD_DATE="1317673868" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation</A><a name="PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation" href="#PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation" style="margin-left: 0.5em;">&para;</a>


  		




  851
  874
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/8.3/static/app-psql.html" name="http://www.postgresql.org/docs/8.3/static/app-psql.html" ADD_DATE="1325722373" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: psql</A><a name="PostgreSQL: Documentation: Manuals: psql" href="#PostgreSQL: Documentation: Manuals: psql" style="margin-left: 0.5em;">&para;</a>


  		




  ......




  1439
  1462
  
    
http://www.alphaworks.ibm.com/tech/db2uriaccess


  		




  1440
  1463
  
    
&quot;


  		




  1441
  1464
  
    
                        </DL><p>


  		




  
  1465
  
    
                        <DT><A HREF="http://en.wikipedia.org/wiki/Hierarchical_and_recursive_queries_in_SQL" name="http://en.wikipedia.org/wiki/Hierarchical_and_recursive_queries_in_SQL" ADD_DATE="1393552874" ICON_URI="http://en.wikipedia.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://en.wikipedia.org/favicon.ico" style="margin-right: 0.5em;"/>Hierarchical and recursive queries in SQL - Wikipedia, the free encyclopedia</A><a name="Hierarchical and recursive queries in SQL - Wikipedia, the free encyclopedia" href="#Hierarchical and recursive queries in SQL - Wikipedia, the free encyclopedia" style="margin-left: 0.5em;">&para;</a>


  		




  
  1466
  
    
<DD>&quot;Recursive CTEs (or &quot;recursive subquery factoring&quot;[15] in Oracle lingo) can be used to traverse relations (as graphs or trees)&quot;


  		




  1442
  1467
  
    
                    </DL><p>


  		




  1443
  1468
  
    
                    <DT><A HREF="http://en.wikipedia.org/wiki/Object-relational_database" name="http://en.wikipedia.org/wiki/Object-relational_database" ADD_DATE="1367483651" ICON_URI="http://bits.wikimedia.org/favicon/wikipedia.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://bits.wikimedia.org/favicon/wikipedia.ico" style="margin-right: 0.5em;"/>Object-relational database - Wikipedia, the free encyclopedia</A><a name="Object-relational database - Wikipedia, the free encyclopedia" href="#Object-relational database - Wikipedia, the free encyclopedia" style="margin-left: 0.5em;">&para;</a>


  		




  1444
  1469
  
    
                </DL><p>


  		












Also available in:  Unified diff