Thanks for your attention and a workaround!
Investigating different types of queries returning the required result I
found out that it fails even on
"SELECT ... FROM t1 CROSS JOIN t2 WHERE t1.b = t2.b ..." although the
18.104.22.168. Joined Tables
FROM T1 CROSS JOIN T2 is equivalent to FROM T1, T2. It is also equivalent to
FROM T1 INNER JOIN T2 ON TRUE (see below).
Unfortunately, my simple suite is mainly for the community to easily
reproduce the problem. In our real applications, we need to utilize OUTER
Since the PostgreSQL next release, 8.3, is on the way now and requires
focusing developers' attention on, please feel free to put all this into the
background; I've risen it up in order to not forget completely :))
""Hiroshi Saito"" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp> wrote in message
> Sorry, very late reaction....Surely it reproduces a problem. It seems that
> it was missed at the time of some problem solutions. Probably, It seems to
> be MOLE-BASHING completely.:-(
> However, The following is the one solution method....
> ' strSql = "SELECT t1.* FROM t1 INNER JOIN t2 ON t1.b = t2.b ORDER BY
> strSql = "SELECT t1.* FROM t1,t2 WHERE t1.b = t2.b ORDER BY t2.c"
> But, Investigation will be continued.
> I appreciate your perseverance. Thanks!
> Hiroshi Saito
In response to
pgsql-odbc by date
|Next:||From: Stephen Frost||Date: 2007-10-03 12:57:09|
|Subject: Filtering ODBC table list|
|Previous:||From: Relyea, Mike||Date: 2007-10-01 23:48:45|
|Subject: Out of memory error|