Thread: Proposal: First step towards Intelligent,integrated database

Proposal: First step towards Intelligent,integrated database

From
ghatpande@vsnl.net
Date:
<font face="Arial"><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"><font face="Calibri">Hello,</font><p
class="MsoNormal"style="MARGIN: 0cm 0cm 0pt"><font face="Calibri"></font> <p class="MsoNormal" style="MARGIN: 0cm 0cm
0pt"><fontface="Calibri">Here is the proposal: <span style="mso-spacerun: yes"> </span>My 1<sup>st</sup> step towards
Intelligent,Integrated database. I am explaining the proposal with the use of example. </font><p class="MsoNormal"
style="MARGIN:0cm 0cm 0pt"><font face="Calibri">Example: We will have a master table say CustMast and a transaction
tablesay salesOrder table.</font><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"><font face="Calibri">View of
CustMast:</font><pclass="MsoNormal" style="MARGIN: 0cm 0cm 0pt 36pt"><font face="Calibri">CustCode<span
style="mso-spacerun:yes">    </span>Number(5),</font><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 36pt"><font
face="Calibri">CustName<spanstyle="mso-spacerun: yes">  </span>Varchar(30),</font><p class="MsoNormal" style="MARGIN:
0cm0cm 0pt 36pt"><font face="Calibri">CustAdrsLine1<span style="mso-spacerun: yes">   </span>Varchar,</font><p
class="MsoNormal"style="MARGIN: 0cm 0cm 0pt 36pt"><font face="Calibri">CustAdrsLine2<span style="mso-spacerun: yes">  
</span>varchar<spanstyle="mso-spacerun: yes">  </span>etc.</font><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"><font
face="Calibri">Viewof SalesOrder:</font><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt 36pt"><font
face="Calibri">Sordno<spanstyle="mso-spacerun: yes">    </span>Number(8),</font><p class="MsoNormal" style="MARGIN: 0cm
0cm0pt 36pt"><font face="Calibri">Sorddt<span style="mso-spacerun: yes">     </span>date,</font><p class="MsoNormal"
style="MARGIN:0cm 0cm 0pt 36pt"><font face="Calibri">CustCode<span style="mso-spacerun: yes">  </span>Number(5)<span
style="mso-spacerun:yes">  </span>-<span style="mso-spacerun: yes">  </span>present way of defining.</font><p
class="MsoNormal"style="MARGIN: 0cm 0cm 0pt"><font face="Calibri"><span style="mso-spacerun: yes"> </span>Proposed way
is:</font><pclass="MsoNormal" style="TEXT-INDENT: 36pt; MARGIN: 0cm 0cm 0pt"><b><font face="Calibri">CustCode Object
CustMast.<spanstyle="mso-spacerun: yes">     </span>--- New data type to be introduced called “O” Object and create
tabledefinition to be modified whenever data type is ‘O’, it will accept object name (in this case table name). Here I
wantto inform data definition that field and its data type is already defined in master table and use the same data
typehere and both tables are linked with this field.</font></b><p class="MsoNormal" style="MARGIN: 0cm 0cm
0pt"><b><fontface="Calibri">We will be using same field name in both tables if not along with table name field name is
tobe accepted in create table definition.</font></b><p class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"><font
face="Calibri">Advantages:</font><p class="MsoListParagraphCxSpFirst" style="TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt
36pt;mso-add-space: auto; mso-list: l0 level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font:
minor-latin"><spanstyle="mso-list: Ignore"><font face="Calibri">1.</font><span style="FONT: 7pt 'Times New
Roman'">      </span></span></span><font face="Calibri">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.</font><p
class="MsoListParagraphCxSpMiddle"style="TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto; mso-list:
l0level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list:
Ignore"><fontface="Calibri">2.</font><span style="FONT: 7pt 'Times New Roman'">       </span></span></span><font
face="Calibri">Inpresent situation select statement for selecting values from join of both tables will be</font><p
class="MsoListParagraphCxSpMiddle"style="MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto"><font face="Calibri">Select
sordno,sorddt, custcode, custname, custadrsline1 </font><p class="MsoListParagraphCxSpMiddle" style="MARGIN: 0cm 0cm
0pt36pt; mso-add-space: auto"><font face="Calibri">from salesorder, custmast </font><p
class="MsoListParagraphCxSpMiddle"style="MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto"><font face="Calibri">where
salesorder.custcode=custmast.custcode.</font><pclass="MsoListParagraphCxSpMiddle" style="TEXT-INDENT: -18pt; MARGIN:
0cm0cm 0pt 36pt; mso-add-space: auto; mso-list: l0 level1 lfo1"><span style="mso-bidi-font-family: Calibri;
mso-bidi-theme-font:minor-latin"><span style="mso-list: Ignore"><font face="Calibri">3.</font><span style="FONT: 7pt
'TimesNew Roman'">       </span></span></span><font face="Calibri">In proposed way we can write this statement
as:</font><pclass="MsoListParagraphCxSpMiddle" style="MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto"><font
face="Calibri">Selectsordno, sorddt, custcode, custname, custadrsline1 </font><p class="MsoListParagraphCxSpMiddle"
style="MARGIN:0cm 0cm 0pt 36pt; mso-add-space: auto"><font face="Calibri">from salesorder<span style="mso-spacerun:
yes"> </span>(with proper changes in program which pickup values from select statement.</font><p
class="MsoListParagraphCxSpMiddle"style="TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto; mso-list:
l0level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list:
Ignore"><fontface="Calibri">4.</font><span style="FONT: 7pt 'Times New Roman'">       </span></span></span><font
face="Calibri">Fieldcan be from another table in same database or from Excel sheet column.</font><p
class="MsoListParagraphCxSpMiddle"style="TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto; mso-list:
l0level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list:
Ignore"><fontface="Calibri">5.</font><span style="FONT: 7pt 'Times New Roman'">       </span></span></span><font
face="Calibri">Viewsneed not be created as all tables are properly linked with each other in an application. </font><p
class="MsoListParagraphCxSpMiddle"style="TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto; mso-list:
l0level1 lfo1"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin"><span style="mso-list:
Ignore"><fontface="Calibri">6.</font><span style="FONT: 7pt 'Times New Roman'">       </span></span></span><font
face="Calibri"><strong>Thisis only first step and many advantages can be a result of brainstorm.</strong> </font><p
class="MsoListParagraphCxSpMiddle"style="TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto; mso-list:
l0level1 lfo1"><font face="Calibri">7.    This will change RDBMS, Tools and ERP to next generation.</font><p
class="MsoListParagraphCxSpMiddle"style="TEXT-INDENT: -18pt; MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto; mso-list:
l0level1 lfo1"><font face="Calibri"></font> <p class="MsoListParagraphCxSpMiddle" style="TEXT-INDENT: -18pt; MARGIN:
0cm0cm 0pt 36pt; mso-add-space: auto; mso-list: l0 level1 lfo1"><font face="Calibri">For any clarifications pl contact.
Plgive your feedback.</font><p class="MsoListParagraphCxSpLast" style="MARGIN: 0cm 0cm 0pt 36pt; mso-add-space:
auto"><spanstyle="mso-spacerun: yes"></span> <p class="MsoListParagraphCxSpLast" style="MARGIN: 0cm 0cm 0pt 36pt;
mso-add-space:auto"><span style="mso-spacerun: yes">Regards Many,</span><p class="MsoListParagraphCxSpLast"
style="MARGIN:0cm 0cm 0pt 36pt; mso-add-space: auto"><span style="mso-spacerun: yes">Vijay Ghatpande.</span><p
class="MsoListParagraphCxSpLast"style="MARGIN: 0cm 0cm 0pt 36pt; mso-add-space: auto"><span style="mso-spacerun:
yes">Cell:+91 9822456142.</span></font> 

Re: Proposal: First step towards Intelligent,integrated database

From
Dann Corbit
Date:

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.

Re: Proposal: First step towards Intelligent, integrateddatabase

From
ghatpande@vsnl.net
Date:
Create domain is only useful for abstracting common constraints on fields into single location for maintenance. It may
notbe 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.
> 


Re: Proposal: First step towards Intelligent,integrated database

From
Pavel Stehule
Date:
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.


Re: Proposal: First step towards Intelligent, integrateddatabase

From
Tom Lane
Date:
ghatpande@vsnl.net writes:
> Create domain is only useful for abstracting common constraints on fields into single location for maintenance. It
maynot 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


Re: Proposal: First step towards Intelligent, integrateddatabase

From
Andrew Dunstan
Date:

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
maynot 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


Re: Proposal: First step towards Intelligent,integrated database

From
David Fetter
Date:
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


Re: Proposal: First step towards Intelligent, integrateddatabase

From
ghatpande@vsnl.net
Date:
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
> 


Re: Proposal: First step towards Intelligent, integrateddatabase

From
David Fetter
Date:
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


Re: Proposal: First step towards Intelligent, integrateddatabase

From
Jim Nasby
Date:
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
maynot 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.
"Thosewho 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
haveto specify exactly how to join the two tables). 
--
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net




Re: Proposal: First step towards Intelligent, integrateddatabase

From
ghatpande@vsnl.net
Date:
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
> 


Re: Proposal: First step towards Intelligent, integrateddatabase

From
Josh Berkus
Date:
> 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
haveto specify exactly how to join the two tables).
 

Already exists:
http://htsql.org/


--                                  -- Josh Berkus                                    PostgreSQL Experts Inc.
                        http://www.pgexperts.com
 


Re: Proposal: First step towards Intelligent, integrated database

From
ghatpande@vsnl.net
Date:
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.
Processortranslates 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
notthe only aim. I am sure that the ultimate output of my proposal is NEXT GENERATION DATABASE. It will change database
andERP 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
> 


Re: Proposal: First step towards Intelligent, integrateddatabase

From
ghatpande@vsnl.net
Date:
If possible can you provide glimpses of History. Corrected History will always help for future. Success rate also
increasesif 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
> 


Re: Proposal: First step towards Intelligent, integrateddatabase

From
ghatpande@vsnl.net
Date:
I know world's population. Non of the person thinks alike and still many peoples goal can be the same. Nothing is
virginin this world. If someone thinks like that then it is a mistake.  My aim is to prove that Postgresql can be the
greatleader 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
> 


Re: Proposal: First step towards Intelligent, integrateddatabase

From
Vaibhav Kaushal
Date:
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?



Re: Proposal: First step towards Intelligent, integrateddatabase

From
"Kevin Grittner"
Date:
<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


Re: Proposal: First step towards Intelligent, integrateddatabase

From
Andrew Dunstan
Date:

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