While I like the optimisation, the SQL syntax seems pretty horrible.
Could it not be done without changing the syntax at all, except to
change slightly how one defines a column? Given something like
CREATE TABLE item_name (
item_id INT PRIMARY KEY,
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> Could you, please, comment the proposal.
Okay: "ugly and unimplementable".
Where are you going to put these back-references that the description
glosses over so quickly? They can't be in the row itself; that doesn't
scale to large numbers of reference
On Thu, 2002-04-04 at 14:17, Oleg Bartunov wrote:
Subject: Bidirectional hard joins
>
> Hi,
>
>
> Here we propose some essential improvement of postgreSQL functionality,
> which may provide a great perfomance increase.
>
> 1. Problem
>
> The fastest way to find and fetch a record from a ta
Tom,
I attached a message from my colleague and think it'd be interesting
to you. A short history: During developing of one project on
Windows platform, Teodor has discovered a pretty nice feature of Gigabase
(free embedded database by Konstantin Knizhnik,
http://www.geocities.com/kknizhnik/gigab
