Received: from localhost (maia-3.hub.org [200.46.204.184])
	by postgresql.org (Postfix) with ESMTP id 0F5599FB724
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Wed, 25 Apr 2007 04:47:29 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024)
	with ESMTP id 47747-03 for <pgsql-sql-postgresql.org@postgresql.org>;
	Wed, 25 Apr 2007 04:47:18 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from smtp2.yandex.ru (smtp2.yandex.ru [213.180.200.18])
	by postgresql.org (Postfix) with ESMTP id C67449FB5E8
	for <pgsql-sql@postgresql.org>; Wed, 25 Apr 2007 04:47:18 -0300 (ADT)
Received: from [82.209.238.118] ([82.209.238.118]:23302 "EHLO asup_tur"
	smtp-auth: "sql4-en" TLS-CIPHER: <none> TLS-PEER-CN1: <none>)
	by mail.yandex.ru with ESMTP id S3375761AbXDYHrM (ORCPT
	<rfc822;pgsql-sql@postgresql.org>); Wed, 25 Apr 2007 11:47:12 +0400
X-Comment: RFC 2476 MSA function at smtp2.yandex.ru logged sender identity as:
	sql4-en
Date: Wed, 25 Apr 2007 10:47:08 +0300
From: Dmitry Turin <sql4-en@narod.ru>
X-Mailer: The Bat! (v2.01) Personal
Reply-To: Dmitry Turin <sql4-en@narod.ru>
X-Priority: 3 (Normal)
Message-ID: <18310248515.20070425104708@narod.ru>
To: pgsql-sql@postgresql.org
Subject: Re: We all are looped on Internet: request + transport = invariant
In-Reply-To: <1177422927.737.113.camel@pampa>
References: <14110647859.20070413105812@narod.ru>
	<20070413150936.GA31517@phlogiston.dyndns.org>
	<1684192906.20070419090827@narod.ru>
	<20070419134808.GB14187@phlogiston.dyndns.org>
	<814860828.20070420120819@narod.ru>  <4628A08F.9050804@archonet.com>
	<1177072978.760.40.camel@pampa>  <7939450187.20070420185808@narod.ru>
	<1177095450.760.71.camel@pampa>  <1312216062.20070423112045@narod.ru>
	<1177329421.737.39.camel@pampa>  <922322078.20070424105126@narod.ru>
	<1177414707.737.69.camel@pampa>  <7519129062.20070424153133@narod.ru>
	<1177422927.737.113.camel@pampa>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.639 tagged_above=0 required=5 tests=AWL=0.638,
	BAYES_50=0.001
X-Spam-Level: 
X-Archive-Number: 200704/239
X-Sequence-Number: 28239

Good day, Joe.

>> J> How do I see employees in just one department?
>> department[id="1"].employee >>;
>> department[name="Technical"].employee >>;
J> How is that any different or better than a standard SQL SELECT

by absence of gasket (php, its library; perl, its library; etc)

J> XML is *not* the only answer to viewing or even "transporting" data.

it's nothing more simply: offer your decision !!

J> others want to see a chart

it's nothing more simply: offer format for data, on which chart will be created !!

J> And there's nothing wrong with Perl, PHP, Python and the myriad
J> interface languages.

I said many times, what is wrong:
applied users can not join sql and perl, can not use libraries,
and can not adjust web-server.

J> I don't see how TML improves

It characterizes not analysed situation, but you.

J> Some people prefer a tabular representation

<tablename field1= field2= field3= >
<tablename field1= field2= field3= >
<tablename field1= field2= field3= >
<tablename field1= field2= field3= >
<tablename field1= field2= field3= >

---

>> J> How do I see a single employee?
>> employee[id="31"] >>;
>> employee[name="Tomson"] >>;
J> I want to see specific columns of the employee row

Mark other fields (columns) by sign "#" to prevent output of them.
NOW there is no construction like
employee#[need_field]
i.e. to forbid all field and to allow necessary columns ("need_field").
Probably i add that.

J> or see the name of the department that Tomson works

department.#employee[name="Tomson"] >>;

or

#employee[name="Tomson"].department >>;

J> or the name of Tomson's manager?

Let table "employee" has additional field "manager"
create table employee {
  id         num      primary key,
  name       string,
  salary     num,
  department num      references department (id),
  manager    bool
};

Request is (look at
http://sql4.by.ru/site/sql40/en/author/determination_eng.htm,
paragraph "Buckle")

(employee[manager=true].#department.#employee[name="Tomson"],
employee[manager=true name="Tomson"]) >>;

or

(#employee[name="Tomson"].#department.employee[manager=true],
employee[manager=true name="Tomson"]) >>;

If you seggest other scheme of data, i will write query for it.

J> This "fictional" attribute of yours implies a change to SQL DDL.

You are worried about technical realization or ideological orthodoxy ?
Or maybe about anything else ?

J> if someone comes along and wants to do
J> SELECT name, SUM(salary) FROM employee GROUP BY name?

create view x as SELECT name, SUM(salary) FROM employee GROUP BY name;
x >>;

J> thousands of users may agree and converge on those choices.

1. Not users, but programmers.
2. Needs are produced also, as goods and capital goods.
     Karl Marks
   For example, look at yourself.


Dmitry Turin
http://html6.by.ru
http://sql4.by.ru
http://computer2.by.ru