Message-ID: <3EF6C3D6.7080904@klaster.net>
Date: Mon, 23 Jun 2003 11:09:42 +0200
From: Tomasz Myrta <jasiek@klaster.net>
User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US;
	rv:1.4b) Gecko/20030507
MIME-Version: 1.0
To: Richard Huxton <dev@archonet.com>
Cc: PGSQL-SQL <pgsql-sql@postgresql.org>
Subject: Re: virtual table
References: <3EF61E44.2020601@klaster.net>
	<200306230929.24372.dev@archonet.com>
	<3EF6BCB4.2040209@klaster.net>
	<200306230954.54185.dev@archonet.com>
In-Reply-To: <200306230954.54185.dev@archonet.com>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit

Dnia 2003-06-23 10:54, Użytkownik Richard Huxton napisał:

> Hmm - I think your problem is going to come before that. Any time you do an 
> INSERT, PostgreSQL is going to need to know the types of all the columns 
> involved.
> 
> For this sort of thing, I try to keep all the related bits (initial function, 
> views, triggers) in the same text-file to encourage me to remember to update 
> them all together.
I also do this - it isn't really difficult with well written scripts. I was 
just wondering if I don't waste my time tracking all the changes.

> 
> It sounds like this table1 is only being used during transfer. Is there any 
> reason why you aren't just inserting the required rows into table2.
My queries are ordinary transportation problems with 0 up to 2 changes. I 
found it's better (for performance reason) to find all possible relations as 
single rows and split them at the end into simple connections. Maybe I should 
dig into this problem again and rewrite my queries...

Regards,
Tomasz Myrta