From: | Tomasz Myrta <jasiek(at)klaster(dot)net> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | PGSQL-SQL <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: virtual table |
Date: | 2003-06-23 09:09:42 |
Message-ID: | 3EF6C3D6.7080904@klaster.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2003-06-23 10:55:02 | Re: Urgent Help : Use of return from function/procedure. |
Previous Message | Richard Huxton | 2003-06-23 08:54:54 | Re: virtual table |