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.
Experience the excellence....
----- Original Message -----
From: Josh Berkus <josh(at)agliodbs(dot)com>
Date: Thursday, December 2, 2010 8:08 am
Subject: Re: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase
To: Jim Nasby <jim(at)nasby(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ghatpande(at)vsnl(dot)net, Dann Corbit <DCorbit(at)connx(dot)com>, pgsql hackers <pgsql-hackers(at)postgresql(dot)org>
> > 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:
> -- Josh Berkus
> PostgreSQL Experts Inc.
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-hackers by date
|Next:||From: Jeff Davis||Date: 2010-12-02 05:27:32|
|Subject: Re: build problem|
|Previous:||From: Robert Haas||Date: 2010-12-02 04:36:42|
|Subject: Re: crash-safe visibility map, take three|