pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedProposal: First step towards Intelligent,integrated database
18+ messages / 10 participants
[nested] [flat]
* Proposal: First step towards Intelligent,integrated database
@ 2010-12-01 10:19 ghatpande@vsnl.net
0 siblings, 3 replies; 18+ messages in thread
From: ghatpande@vsnl.net @ 2010-12-01 10:19 UTC (permalink / raw)
To: pgsql-hackers
Hello,
Here is the proposal: My 1st step towards Intelligent, Integrated database. I am explaining the proposal with the use of example.
Example: We will have a master table say CustMast and a transaction table say salesOrder table.
View of CustMast:
CustCode Number(5),
CustName Varchar(30),
CustAdrsLine1 Varchar,
CustAdrsLine2 varchar etc.
View of SalesOrder:
Sordno Number(8),
Sorddt date,
CustCode Number(5) - present way of defining.
Proposed way is:
CustCode Object CustMast. --- New data type to be introduced called “O” Object and create table definition to be modified whenever data type is ‘O’, it will accept object name (in this case table name). Here I want to inform data definition that field and its data type is already defined in master table and use the same data type here and both tables are linked with this field.
We will be using same field name in both tables if not along with table name field name is to be accepted in create table definition.
Advantages:
1. Now database knows that custcode in salesorder is a foreign key, a table constraint can be created. It also knows that index to be created on this field.
2. In present situation select statement for selecting values from join of both tables will be
Select sordno, sorddt, custcode, custname, custadrsline1
from salesorder, custmast
where salesorder.custcode=custmast.custcode.
3. In proposed way we can write this statement as:
Select sordno, sorddt, custcode, custname, custadrsline1
from salesorder (with proper changes in program which pickup values from select statement.
4. Field can be from another table in same database or from Excel sheet column.
5. Views need not be created as all tables are properly linked with each other in an application.
6. This is only first step and many advantages can be a result of brainstorm.
7. This will change RDBMS, Tools and ERP to next generation.
For any clarifications pl contact. Pl give your feedback.
Regards Many,
Vijay Ghatpande.
Cell: +91 9822456142.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent,integrated database
@ 2010-12-01 10:34 Dann Corbit <DCorbit@connx.com>
parent: ghatpande@vsnl.net
2 siblings, 1 reply; 18+ messages in thread
From: Dann Corbit @ 2010-12-01 10:34 UTC (permalink / raw)
To: 'ghatpande@vsnl.net' <ghatpande@vsnl.net>; pgsql-hackers
I am probably just being thick, but how is your idea different from create domain:
http://www.postgresql.org/docs/current/static/sql-createdomain.html
From: pgsql-hackers-owner@postgresql.org [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of ghatpande@vsnl.net
Sent: Wednesday, December 01, 2010 2:20 AM
To: pgsql hackers
Subject: [HACKERS] Proposal: First step towards Intelligent,integrated database
Importance: High
Hello,
Here is the proposal: My 1st step towards Intelligent, Integrated database. I am explaining the proposal with the use of example.
Example: We will have a master table say CustMast and a transaction table say salesOrder table.
View of CustMast:
CustCode Number(5),
CustName Varchar(30),
CustAdrsLine1 Varchar,
CustAdrsLine2 varchar etc.
View of SalesOrder:
Sordno Number(8),
Sorddt date,
CustCode Number(5) - present way of defining.
Proposed way is:
CustCode Object CustMast. --- New data type to be introduced called "O" Object and create table definition to be modified whenever data type is 'O', it will accept object name (in this case table name). Here I want to inform data definition that field and its data type is already defined in master table and use the same data type here and both tables are linked with this field.
We will be using same field name in both tables if not along with table name field name is to be accepted in create table definition.
Advantages:
1. Now database knows that custcode in salesorder is a foreign key, a table constraint can be created. It also knows that index to be created on this field.
2. In present situation select statement for selecting values from join of both tables will be
Select sordno, sorddt, custcode, custname, custadrsline1
from salesorder, custmast
where salesorder.custcode=custmast.custcode.
3. In proposed way we can write this statement as:
Select sordno, sorddt, custcode, custname, custadrsline1
from salesorder (with proper changes in program which pickup values from select statement.
4. Field can be from another table in same database or from Excel sheet column.
5. Views need not be created as all tables are properly linked with each other in an application.
6. This is only first step and many advantages can be a result of brainstorm.
7. This will change RDBMS, Tools and ERP to next generation.
For any clarifications pl contact. Pl give your feedback.
Regards Many,
Vijay Ghatpande.
Cell: +91 9822456142.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-01 10:46 ghatpande@vsnl.net
parent: Dann Corbit <DCorbit@connx.com>
0 siblings, 1 reply; 18+ messages in thread
From: ghatpande@vsnl.net @ 2010-12-01 10:46 UTC (permalink / raw)
To: Dann Corbit <DCorbit@connx.com>; +Cc: pgsql-hackers
Create domain is only useful for abstracting common constraints on fields into single location for maintenance. It may not be useful to link tables.
----- Original Message -----
From: Dann Corbit <DCorbit@connx.com>
Date: Wednesday, December 1, 2010 4:04 pm
Subject: RE: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase
To: "'ghatpande@vsnl.net'" <ghatpande@vsnl.net>, pgsql hackers <pgsql-hackers@postgresql.org>
> I am probably just being thick, but how is your idea different
> from create domain:
> http://www.postgresql.org/docs/current/static/sql-createdomain.html
>
>
> From: pgsql-hackers-owner@postgresql.org [mailto:pgsql-hackers-
> owner@postgresql.org] On Behalf Of ghatpande@vsnl.net
> Sent: Wednesday, December 01, 2010 2:20 AM
> To: pgsql hackers
> Subject: [HACKERS] Proposal: First step towards
> Intelligent,integrated database
> Importance: High
>
> Hello,
>
> Here is the proposal: My 1st step towards Intelligent, Integrated
> database. I am explaining the proposal with the use of example.
> Example: We will have a master table say CustMast and a
> transaction table say salesOrder table.
> View of CustMast:
> CustCode Number(5),
> CustName Varchar(30),
> CustAdrsLine1 Varchar,
> CustAdrsLine2 varchar etc.
> View of SalesOrder:
> Sordno Number(8),
> Sorddt date,
> CustCode Number(5) - present way of defining.
> Proposed way is:
> CustCode Object CustMast. --- New data type to be introduced
> called "O" Object and create table definition to be modified
> whenever data type is 'O', it will accept object name (in this
> case table name). Here I want to inform data definition that field
> and its data type is already defined in master table and use the
> same data type here and both tables are linked with this field.
> We will be using same field name in both tables if not along with
> table name field name is to be accepted in create table definition.
> Advantages:
>
> 1. Now database knows that custcode in salesorder is a
> foreign key, a table constraint can be created. It also knows that
> index to be created on this field.
>
> 2. In present situation select statement for selecting
> values from join of both tables will be
>
> Select sordno, sorddt, custcode, custname, custadrsline1
>
> from salesorder, custmast
>
> where salesorder.custcode=custmast.custcode.
>
> 3. In proposed way we can write this statement as:
>
> Select sordno, sorddt, custcode, custname, custadrsline1
>
> from salesorder (with proper changes in program which pickup
> values from select statement.
>
> 4. Field can be from another table in same database or from
> Excel sheet column.
>
> 5. Views need not be created as all tables are properly
> linked with each other in an application.
>
> 6. This is only first step and many advantages can be a
> result of brainstorm.
>
> 7. This will change RDBMS, Tools and ERP to next generation.
>
>
>
> For any clarifications pl contact. Pl give your feedback.
>
>
>
> Regards Many,
>
> Vijay Ghatpande.
>
> Cell: +91 9822456142.
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent,integrated database
@ 2010-12-01 13:41 Pavel Stehule <pavel.stehule@gmail.com>
parent: ghatpande@vsnl.net
2 siblings, 0 replies; 18+ messages in thread
From: Pavel Stehule @ 2010-12-01 13:41 UTC (permalink / raw)
To: ghatpande@vsnl.net; +Cc: pgsql-hackers
Hello
there was a very similar design in ANSI SQL 99. I have documentation
only in Czech, but probably you can find a sources about OOP part in
ANSI/SQL.
CREATE TABLE children(
id int primary key,
parent ref(parents)
name ..
...
and you can write queries like
SELECT name, parent->name FROM children
Regards
Pavel Stehule
see a object support in ANSI/SQL - keywords ref, scope,
2010/12/1 <ghatpande@vsnl.net>:
> Hello,
>
>
>
> Here is the proposal: My 1st step towards Intelligent, Integrated database.
> I am explaining the proposal with the use of example.
>
> Example: We will have a master table say CustMast and a transaction table
> say salesOrder table.
>
> View of CustMast:
>
> CustCode Number(5),
>
> CustName Varchar(30),
>
> CustAdrsLine1 Varchar,
>
> CustAdrsLine2 varchar etc.
>
> View of SalesOrder:
>
> Sordno Number(8),
>
> Sorddt date,
>
> CustCode Number(5) - present way of defining.
>
> Proposed way is:
>
> CustCode Object CustMast. --- New data type to be introduced called “O”
> Object and create table definition to be modified whenever data type is ‘O’,
> it will accept object name (in this case table name). Here I want to inform
> data definition that field and its data type is already defined in master
> table and use the same data type here and both tables are linked with this
> field.
>
> We will be using same field name in both tables if not along with table name
> field name is to be accepted in create table definition.
>
> Advantages:
>
> 1. Now database knows that custcode in salesorder is a foreign key, a
> table constraint can be created. It also knows that index to be created on
> this field.
>
> 2. In present situation select statement for selecting values from
> join of both tables will be
>
> Select sordno, sorddt, custcode, custname, custadrsline1
>
> from salesorder, custmast
>
> where salesorder.custcode=custmast.custcode.
>
> 3. In proposed way we can write this statement as:
>
> Select sordno, sorddt, custcode, custname, custadrsline1
>
> from salesorder (with proper changes in program which pickup values from
> select statement.
>
> 4. Field can be from another table in same database or from Excel
> sheet column.
>
> 5. Views need not be created as all tables are properly linked with
> each other in an application.
>
> 6. This is only first step and many advantages can be a result of
> brainstorm.
>
> 7. This will change RDBMS, Tools and ERP to next generation.
>
>
>
> For any clarifications pl contact. Pl give your feedback.
>
>
>
> Regards Many,
>
> Vijay Ghatpande.
>
> Cell: +91 9822456142.
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-01 14:41 Tom Lane <tgl@sss.pgh.pa.us>
parent: ghatpande@vsnl.net
0 siblings, 2 replies; 18+ messages in thread
From: Tom Lane @ 2010-12-01 14:41 UTC (permalink / raw)
To: ghatpande@vsnl.net; +Cc: Dann Corbit <DCorbit@connx.com>; pgsql-hackers
ghatpande@vsnl.net writes:
> Create domain is only useful for abstracting common constraints on fields into single location for maintenance. It may not be useful to link tables.
It's still unclear what this does that you don't get from inheritance,
typed tables, use of a table's rowtype as a field type, or CREATE TABLE
LIKE. This isn't exactly virgin territory.
regards, tom lane
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-01 14:59 Andrew Dunstan <andrew@dunslane.net>
parent: Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 2 replies; 18+ messages in thread
From: Andrew Dunstan @ 2010-12-01 14:59 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: ghatpande@vsnl.net, Dann Corbit <DCorbit@connx.com>; pgsql-hackers
On 12/01/2010 09:41 AM, Tom Lane wrote:
> ghatpande@vsnl.net writes:
>> Create domain is only useful for abstracting common constraints on fields into single location for maintenance. It may not be useful to link tables.
> It's still unclear what this does that you don't get from inheritance,
> typed tables, use of a table's rowtype as a field type, or CREATE TABLE
> LIKE. This isn't exactly virgin territory.
>
>
Yeah. Actually, the whole thing reminded me somewhat of the pre-RDBMS
data stores I worked with 25 years or so ago. "Those who cannot remember
history are doomed to repeat it."
cheers
andrew
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent,integrated database
@ 2010-12-01 15:11 David Fetter <david@fetter.org>
parent: ghatpande@vsnl.net
2 siblings, 1 reply; 18+ messages in thread
From: David Fetter @ 2010-12-01 15:11 UTC (permalink / raw)
To: ghatpande@vsnl.net; +Cc: pgsql-hackers
On Wed, Dec 01, 2010 at 03:19:32PM +0500, ghatpande@vsnl.net wrote:
> Hello,
>
> Here is the proposal: My 1st step towards Intelligent, Integrated database.
You're implying that databases are stupid and incoherent. This is
*not* a great way to start.
Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-01 15:15 ghatpande@vsnl.net
parent: David Fetter <david@fetter.org>
0 siblings, 1 reply; 18+ messages in thread
From: ghatpande@vsnl.net @ 2010-12-01 15:15 UTC (permalink / raw)
To: David Fetter <david@fetter.org>; +Cc: pgsql-hackers
Be positive ... Negative thoughts are not good...
----- Original Message -----
From: David Fetter <david@fetter.org>
Date: Wednesday, December 1, 2010 8:42 pm
Subject: Re: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase
To: ghatpande@vsnl.net
Cc: pgsql hackers <pgsql-hackers@postgresql.org>
> On Wed, Dec 01, 2010 at 03:19:32PM +0500, ghatpande@vsnl.net wrote:
> > Hello,
> >
> > Here is the proposal: My 1st step towards Intelligent,
> Integrated database.
>
> You're implying that databases are stupid and incoherent. This is
> *not* a great way to start.
>
> Cheers,
> David.
> --
> David Fetter <david@fetter.org> http://fetter.org/
> Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
> Skype: davidfetter XMPP: david.fetter@gmail.com
> iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
>
> Remember to vote!
> Consider donating to Postgres: http://www.postgresql.org/about/donate
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-01 15:59 David Fetter <david@fetter.org>
parent: ghatpande@vsnl.net
0 siblings, 1 reply; 18+ messages in thread
From: David Fetter @ 2010-12-01 15:59 UTC (permalink / raw)
To: ghatpande@vsnl.net; +Cc: pgsql-hackers
My point exactly. You started off with high negativity, and you
should not expect good results from same.
Cheers,
David.
On Wed, Dec 01, 2010 at 08:15:25PM +0500, ghatpande@vsnl.net wrote:
> Be positive ... Negative thoughts are not good...
>
> ----- Original Message -----
> From: David Fetter <david@fetter.org>
> Date: Wednesday, December 1, 2010 8:42 pm
> Subject: Re: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase
> To: ghatpande@vsnl.net
> Cc: pgsql hackers <pgsql-hackers@postgresql.org>
>
> > On Wed, Dec 01, 2010 at 03:19:32PM +0500, ghatpande@vsnl.net wrote:
> > > Hello,
> > >
> > > Here is the proposal: My 1st step towards Intelligent,
> > Integrated database.
> >
> > You're implying that databases are stupid and incoherent. This is
> > *not* a great way to start.
> >
> > Cheers,
> > David.
> > --
> > David Fetter <david@fetter.org> http://fetter.org/
> > Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
> > Skype: davidfetter XMPP: david.fetter@gmail.com
> > iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
> >
> > Remember to vote!
> > Consider donating to Postgres: http://www.postgresql.org/about/donate
> >
> > --
> > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> > To make changes to your subscription:
> > http://www.postgresql.org/mailpref/pgsql-hackers
> >
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-02 00:22 Jim Nasby <jim@nasby.net>
parent: Andrew Dunstan <andrew@dunslane.net>
1 sibling, 1 reply; 18+ messages in thread
From: Jim Nasby @ 2010-12-02 00:22 UTC (permalink / raw)
To: Andrew Dunstan <andrew@dunslane.net>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; ghatpande@vsnl.net, Dann Corbit <DCorbit@connx.com>; pgsql-hackers
On Dec 1, 2010, at 8:59 AM, Andrew Dunstan wrote:
> On 12/01/2010 09:41 AM, Tom Lane wrote:
>> ghatpande@vsnl.net writes:
>>> Create domain is only useful for abstracting common constraints on fields into single location for maintenance. It may not be useful to link tables.
>> It's still unclear what this does that you don't get from inheritance,
>> typed tables, use of a table's rowtype as a field type, or CREATE TABLE
>> LIKE. This isn't exactly virgin territory.
>>
>>
>
> Yeah. Actually, the whole thing reminded me somewhat of the pre-RDBMS data stores I worked with 25 years or so ago. "Those who cannot remember history are doomed to repeat it."
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).
--
Jim C. Nasby, Database Architect jim@nasby.net
512.569.9461 (cell) http://jim.nasby.net
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-02 02:11 ghatpande@vsnl.net
parent: David Fetter <david@fetter.org>
0 siblings, 0 replies; 18+ messages in thread
From: ghatpande@vsnl.net @ 2010-12-02 02:11 UTC (permalink / raw)
To: David Fetter <david@fetter.org>; +Cc: pgsql-hackers
No negativity. This world is beautiful, I want to make it more beautiful. Together we can make it, I am sure.
Cheers,
Vijay.
Experience the excellence
----- Original Message -----
From: David Fetter <david@fetter.org>
Date: Wednesday, December 1, 2010 9:30 pm
Subject: Re: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase
To: ghatpande@vsnl.net
Cc: pgsql hackers <pgsql-hackers@postgresql.org>
> My point exactly. You started off with high negativity, and you
> should not expect good results from same.
>
> Cheers,
> David.
> On Wed, Dec 01, 2010 at 08:15:25PM +0500, ghatpande@vsnl.net wrote:
> > Be positive ... Negative thoughts are not good...
> >
> > ----- Original Message -----
> > From: David Fetter <david@fetter.org>
> > Date: Wednesday, December 1, 2010 8:42 pm
> > Subject: Re: [HACKERS] Proposal: First step towards
> Intelligent,integrateddatabase> To: ghatpande@vsnl.net
> > Cc: pgsql hackers <pgsql-hackers@postgresql.org>
> >
> > > On Wed, Dec 01, 2010 at 03:19:32PM +0500, ghatpande@vsnl.net
> wrote:> > > Hello,
> > > >
> > > > Here is the proposal: My 1st step towards Intelligent,
> > > Integrated database.
> > >
> > > You're implying that databases are stupid and incoherent.
> This is
> > > *not* a great way to start.
> > >
> > > Cheers,
> > > David.
> > > --
> > > David Fetter <david@fetter.org> http://fetter.org/
> > > Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
> > > Skype: davidfetter XMPP: david.fetter@gmail.com
> > > iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
> > >
> > > Remember to vote!
> > > Consider donating to Postgres:
> http://www.postgresql.org/about/donate; >
> > > --
> > > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> > > To make changes to your subscription:
> > > http://www.postgresql.org/mailpref/pgsql-hackers
> > >
> >
> > --
> > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> > To make changes to your subscription:
> > http://www.postgresql.org/mailpref/pgsql-hackers
>
> --
> David Fetter <david@fetter.org> http://fetter.org/
> Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
> Skype: davidfetter XMPP: david.fetter@gmail.com
> iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
>
> Remember to vote!
> Consider donating to Postgres: http://www.postgresql.org/about/donate
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-02 02:38 Josh Berkus <josh@agliodbs.com>
parent: Jim Nasby <jim@nasby.net>
0 siblings, 1 reply; 18+ messages in thread
From: Josh Berkus @ 2010-12-02 02:38 UTC (permalink / raw)
To: Jim Nasby <jim@nasby.net>; +Cc: Andrew Dunstan <andrew@dunslane.net>; Tom Lane <tgl@sss.pgh.pa.us>; ghatpande@vsnl.net, Dann Corbit <DCorbit@connx.com>; 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
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrated database
@ 2010-12-02 05:18 ghatpande@vsnl.net
parent: Josh Berkus <josh@agliodbs.com>
0 siblings, 0 replies; 18+ messages in thread
From: ghatpande@vsnl.net @ 2010-12-02 05:18 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: Jim Nasby <jim@nasby.net>; Andrew Dunstan <andrew@dunslane.net>; Tom Lane <tgl@sss.pgh.pa.us>; Dann Corbit <DCorbit@connx.com>; pgsql-hackers
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 <josh@agliodbs.com>
Date: Thursday, December 2, 2010 8:08 am
Subject: Re: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase
To: Jim Nasby <jim@nasby.net>
Cc: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, ghatpande@vsnl.net, Dann Corbit <DCorbit@connx.com>, pgsql hackers <pgsql-hackers@postgresql.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:
> 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
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-02 07:29 ghatpande@vsnl.net
parent: Andrew Dunstan <andrew@dunslane.net>
1 sibling, 1 reply; 18+ messages in thread
From: ghatpande@vsnl.net @ 2010-12-02 07:29 UTC (permalink / raw)
To: Andrew Dunstan <andrew@dunslane.net>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Dann Corbit <DCorbit@connx.com>; pgsql-hackers
If possible can you provide glimpses of History. Corrected History will always help for future. Success rate also increases if we could avoid mistakes we made in history.
regards,
Vijay.
Experience the Excellence......
----- Original Message -----
From: Andrew Dunstan <andrew@dunslane.net>
Date: Wednesday, December 1, 2010 8:32 pm
Subject: Re: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: ghatpande@vsnl.net, Dann Corbit <DCorbit@connx.com>, pgsql hackers <pgsql-hackers@postgresql.org>
>
>
> On 12/01/2010 09:41 AM, Tom Lane wrote:
> > ghatpande@vsnl.net writes:
> >> Create domain is only useful for abstracting common constraints
> on fields into single location for maintenance. It may not be
> useful to link tables.
> > It's still unclear what this does that you don't get from
> inheritance,> typed tables, use of a table's rowtype as a field
> type, or CREATE TABLE
> > LIKE. This isn't exactly virgin territory.
> >
> >
>
> Yeah. Actually, the whole thing reminded me somewhat of the pre-
> RDBMS
> data stores I worked with 25 years or so ago. "Those who cannot
> remember
> history are doomed to repeat it."
>
> cheers
>
> andrew
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-02 07:48 ghatpande@vsnl.net
parent: Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 1 reply; 18+ messages in thread
From: ghatpande@vsnl.net @ 2010-12-02 07:48 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Dann Corbit <DCorbit@connx.com>; pgsql-hackers
I know world's population. Non of the person thinks alike and still many peoples goal can be the same. Nothing is virgin in this world. If someone thinks like that then it is a mistake. My aim is to prove that Postgresql can be the great leader if we put natural intelligence in database which is missing all over.
Regards,
Vijay.
Experience the Excellence......
----- Original Message -----
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wednesday, December 1, 2010 8:20 pm
Subject: Re: [HACKERS] Proposal: First step towards Intelligent,integrateddatabase
To: ghatpande@vsnl.net
Cc: Dann Corbit <DCorbit@connx.com>, pgsql hackers <pgsql-hackers@postgresql.org>
> ghatpande@vsnl.net writes:
> > Create domain is only useful for abstracting common constraints
> on fields into single location for maintenance. It may not be
> useful to link tables.
>
> It's still unclear what this does that you don't get from inheritance,
> typed tables, use of a table's rowtype as a field type, or CREATE
> TABLELIKE. This isn't exactly virgin territory.
>
> regards, tom lane
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-02 08:03 Vaibhav Kaushal <vaibhavkaushal123@gmail.com>
parent: ghatpande@vsnl.net
0 siblings, 0 replies; 18+ messages in thread
From: Vaibhav Kaushal @ 2010-12-02 08:03 UTC (permalink / raw)
To: ghatpande@vsnl.net; +Cc: pgsql-hackers
I know world's population. Non of the person thinks alike and still many
peoples goal can be the same. Nothing is virgin in this world. If
someone thinks like that then it is a mistake. My aim is to prove that
Postgresql can be the great leader if we put natural intelligence in
database which is missing all over.
And what is that intelligence?
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-02 17:44 Kevin Grittner <Kevin.Grittner@wicourts.gov>
parent: ghatpande@vsnl.net
0 siblings, 1 reply; 18+ messages in thread
From: Kevin Grittner @ 2010-12-02 17:44 UTC (permalink / raw)
To: ghatpande@vsnl.net; +Cc: Dann Corbit <DCorbit@connx.com>; pgsql-hackers; Tom Lane <tgl@sss.pgh.pa.us>
<ghatpande@vsnl.net> wrote:
> If possible can you provide glimpses of History.
http://en.wikipedia.org/wiki/Navigational_database
http://en.wikipedia.org/wiki/MARK_IV_%28software%29
I don't want to go back there, myself. YMMV.
-Kevin
^ permalink raw reply [nested|flat] 18+ messages in thread
* Re: Proposal: First step towards Intelligent, integrateddatabase
@ 2010-12-02 17:59 Andrew Dunstan <andrew@dunslane.net>
parent: Kevin Grittner <Kevin.Grittner@wicourts.gov>
0 siblings, 0 replies; 18+ messages in thread
From: Andrew Dunstan @ 2010-12-02 17:59 UTC (permalink / raw)
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>; +Cc: ghatpande@vsnl.net, Dann Corbit <DCorbit@connx.com>; pgsql-hackers; Tom Lane <tgl@sss.pgh.pa.us>
On 12/02/2010 12:44 PM, Kevin Grittner wrote:
> <ghatpande@vsnl.net> wrote:
>
>> If possible can you provide glimpses of History.
>
> http://en.wikipedia.org/wiki/Navigational_database
>
> http://en.wikipedia.org/wiki/MARK_IV_%28software%29
>
> I don't want to go back there, myself. YMMV.
>
>
Me either. BTDTGTTS. :-)
cheers
andrew
^ permalink raw reply [nested|flat] 18+ messages in thread
end of thread, other threads:[~2010-12-02 17:59 UTC | newest]
Thread overview: 18+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-12-01 10:19 Proposal: First step towards Intelligent,integrated database ghatpande@vsnl.net
2010-12-01 10:34 ` Dann Corbit <DCorbit@connx.com>
2010-12-01 10:46 ` Re: Proposal: First step towards Intelligent, integrateddatabase ghatpande@vsnl.net
2010-12-01 14:41 ` Re: Proposal: First step towards Intelligent, integrateddatabase Tom Lane <tgl@sss.pgh.pa.us>
2010-12-01 14:59 ` Re: Proposal: First step towards Intelligent, integrateddatabase Andrew Dunstan <andrew@dunslane.net>
2010-12-02 00:22 ` Re: Proposal: First step towards Intelligent, integrateddatabase Jim Nasby <jim@nasby.net>
2010-12-02 02:38 ` Re: Proposal: First step towards Intelligent, integrateddatabase Josh Berkus <josh@agliodbs.com>
2010-12-02 05:18 ` Re: Proposal: First step towards Intelligent, integrated database ghatpande@vsnl.net
2010-12-02 07:29 ` Re: Proposal: First step towards Intelligent, integrateddatabase ghatpande@vsnl.net
2010-12-02 17:44 ` Re: Proposal: First step towards Intelligent, integrateddatabase Kevin Grittner <Kevin.Grittner@wicourts.gov>
2010-12-02 17:59 ` Re: Proposal: First step towards Intelligent, integrateddatabase Andrew Dunstan <andrew@dunslane.net>
2010-12-02 07:48 ` Re: Proposal: First step towards Intelligent, integrateddatabase ghatpande@vsnl.net
2010-12-02 08:03 ` Re: Proposal: First step towards Intelligent, integrateddatabase Vaibhav Kaushal <vaibhavkaushal123@gmail.com>
2010-12-01 13:41 ` Pavel Stehule <pavel.stehule@gmail.com>
2010-12-01 15:11 ` David Fetter <david@fetter.org>
2010-12-01 15:15 ` Re: Proposal: First step towards Intelligent, integrateddatabase ghatpande@vsnl.net
2010-12-01 15:59 ` Re: Proposal: First step towards Intelligent, integrateddatabase David Fetter <david@fetter.org>
2010-12-02 02:11 ` Re: Proposal: First step towards Intelligent, integrateddatabase ghatpande@vsnl.net
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox