Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E34681337999 for ; Thu, 2 Dec 2010 01:19:42 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 85544-02 for ; Thu, 2 Dec 2010 05:19:35 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from fe3.vsnl.net (fe3.vsnl.net [203.200.235.173]) by mail.postgresql.org (Postfix) with ESMTP id 59E35133740B for ; Thu, 2 Dec 2010 01:19:34 -0400 (AST) Received: from vsnl.net ([172.16.28.44]) by fe3.internal.vsnl.net (vsnl mail server fe3) with ESMTP id <0LCS00H59C2VBN30@fe3.internal.vsnl.net> for pgsql-hackers@postgresql.org; Thu, 02 Dec 2010 10:48:31 +0530 (IST) Received: from [172.16.28.177] (Forwarded-For: [117.195.35.112]) by store3.internal.vsnl.net (mshttpd); Thu, 02 Dec 2010 10:18:31 +0500 Date: Thu, 02 Dec 2010 10:18:31 +0500 From: ghatpande@vsnl.net Subject: Re: Proposal: First step towards Intelligent, integrated database In-reply-to: <4CF70690.6050703@agliodbs.com> To: Josh Berkus Cc: Jim Nasby , Andrew Dunstan , Tom Lane , Dann Corbit , pgsql hackers Message-id: MIME-version: 1.0 X-Mailer: Sun Java(tm) System Messenger Express 6.2-6.01 (built Apr 3 2006) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en References: <"87F42982BF2B434F831FCEF4C45FC33 E4209B193"@EXCHANGE.corporate.connx.com> <15327.1291214468@sss.pgh.pa.us> <4CF662C5.70109@dunslane.net> <4FDE4580-04F7-4530-BDBE-078BD91321AA@nasby.net> <4CF70690.6050703@agliodbs.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.909 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RFC_ABUSE_POST=0.001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201012/134 X-Sequence-Number: 175396 The aim of HTSQL is only to avoid joins. Need to setup HTSQL server. On startup introspects table relationships. Relationships are edges in a graph model. Processor translates graph requests into SQL. Some limitations: No custom commands, primitive formatters. Query results are not streaming. No way to override catalog configuration. My proposal has no limitations. Its primary aim is to make database intelligent. Avoiding joins is one of the aim and not the only aim. I am sure that the ultimate output of my proposal is NEXT GENERATION DATABASE. It will change database and ERP world. regards, Vijay. Experience the excellence.... ----- Original Message ----- From: Josh Berkus Date: Thursday, December 2, 2010 8:08 am Subject: Re: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase To: Jim Nasby Cc: Andrew Dunstan , Tom Lane , ghatpande@vsnl.net, Dann Corbit , pgsql hackers > > > Something that did what Pavel mentioned: > > > > SELECT name, parent->name FROM children; > > > > would be very useful. It means you no longer have to write > explicit joins (or perhaps more accurately, you no longer have to > specify exactly how to join the two tables). > > Already exists: > http://htsql.org/ > > > -- > -- Josh Berkus > PostgreSQL Experts Inc. > http://www.pgexperts.com > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers >