Re: constraint upon view

From: Pierre Emmanuel Gros <Pierre-Emmanuel(dot)Gros(at)limsi(dot)fr>
To: Jonathan Gardner <jgardner(at)jonathangardner(dot)net>
Cc: Pierre Emmanuel Gros <Pierre-Emmanuel(dot)Gros(at)limsi(dot)fr>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: constraint upon view
Date: 2004-06-15 16:24:22
Message-ID: 40CF22B6.5090200@limsi.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

In fact i want this kind of view , because my views are forms with a
jdbc selection like

create view toto (integer,integer) as SELECT a,b FROM executeJDBC(jdbc
connection,jdbc uri, 'select a,b from toto');

Where the view toto is filled by the function executeJDBC (jdbc driver,
jdbc uri, remote query )

The problem is i lose to much information about my remote table (primary
key, indexes...) to make good JOIN operation.(for big table , this join
operation
without information upon primary key are very slow...)

So i like to extends the create view syntax to add constraint
information , and i hope speed up my join operation.

I would like to know what to change in the source to obtain this extension .
Pierre
PS excuse me if i was not clear.

Jonathan Gardner wrote:

>On Monday 31 May 2004 06:38 am, Pierre Emmanuel Gros wrote:
>
>
>>Hi,
>>I would like to know if i can add constraint and typed column upon a
>>create view sentence.
>>something like create view toto (a INTEGER primary key , b VARCHAR) as
>>select .....
>>If it is not possible , what to have to change in the backend sources to
>>obtain the result ???
>>
>>
>>
>
>I don't think you want a view in this case. When you select against a view,
>the view is unrolled into the statement that forms it. Try a look at the
>results of "EXPLAIN ANALYZE" when you are selecting against a view.
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2004-06-15 16:43:42 Re: #postgresql report
Previous Message Stephen Frost 2004-06-15 15:48:32 Re: #postgresql report