On Mon, Jul 11, 2011 at 10:12 AM, Florian Pflug <fgp@xxxxxxxx> wrote: > On Jul11, 2011, at 07:08 , Darren Duncan wrote: >> Christopher Browne wrote: >>> Vis-a-vis the attempt to do nested naming, that is "ns1.ns2.table1", >>> there's a pretty good reason NOT to support that, namely that this >>> breaks relational handling of tables. PostgreSQL is a *relational* >>> database system, hence it's preferable for structures to be >>> relational, as opposed to hierarchical, which is what any of the >>> suggested nestings are. >> >> A relational database is a database in which all data is kept in >> relation-typed variables, which SQL calls tables, and you can perform >> all queries and updates with just relation-valued expressions and >> statements. >> >> Organizing the tables into a multi-level namespace, either fixed-depth >> or variable-depth, rather than using a flat namespace, does not make >> the database any less relational, because the above definition and >> any others still hold. > > The point was not, I think, that tables aren't suddenly relations once > namespaces are nested, but that the data model of the dbms *itself*, > i.e. the data model that defines the relationship between namespaces, > types, columns, type, ... becomes harder to map to the relational model. Just so. It's not that it suddenly "becomes no longer relational". Rather, the argument is that "it was intentional for the structuring of table naming to, itself, be relational," and changing that definitely has some undesirable characteristics. The need for recursive queries is the most obvious "undesirable", but it's not the only undesirable thing, by any means. Sure, there's some cool stuff that we can get out of nested namespaces, but I think we'd pay a pretty big price for it, and it shouldn't be treated as "obvious" that: a) It's a good thing to do so, b) It is desirable to do so, c) There will be agreement to do so. To the contrary, there are pretty good reasons to reject the idea. -- When confronted by a difficult problem, solve it by reducing it to the question, "How would the Lone Ranger handle this?" -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
