Skip site navigation (1) Skip section navigation (2)

Re: Proposal: First step towards Intelligent,integrated database

From: Dann Corbit <DCorbit(at)connx(dot)com>
To: "'ghatpande(at)vsnl(dot)net'" <ghatpande(at)vsnl(dot)net>, pgsql hackers<pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: First step towards Intelligent,integrated database
Date: 2010-12-01 10:34:03
Message-ID: 87F42982BF2B434F831FCEF4C45FC33E4209B193@EXCHANGE.corporate.connx.com (view raw or flat)
Thread:
Lists: 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(at)postgresql(dot)org [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of ghatpande(at)vsnl(dot)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.

In response to

Responses

pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2010-12-01 10:35:50
Subject: Re: We really ought to do something about O_DIRECT and data=journalled on ext4
Previous:From: Dimitri FontaineDate: 2010-12-01 10:22:52
Subject: Re: KNNGIST next step: adjusting indexAM API

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group