used in either subquery or view
definition, return
value_fld | flag
---+--
a | true
b | true
c | true
d | true
In Oracle these queries, (rewirtten according to Oracle outer join syntax)
return same result.
--
Victor Wagner
I cannot insert into key field of some table russian words
for this (ETO) and what(CHTO).
Problem doesn't occur on Linux with ru_RU.CP1251 locale
Locale itself is correctly written
perl script
---
use locale;
print (("\375\362\356" eq "\367\362\356")?1:0,"\n")
execution
It would be be very nice feature if upon CREATE FUNCTION statement
these checks would be performed.
--
Victor Wagner [EMAIL PROTECTED]
Chief Technical Officer Office:7-(095)-748-53-88
Communiware.Net Home: 7-(095)-135-46-61
http
n ascii characters only.
PostgreSQL version 7.2.0.
BTW, if I use item left outer join author, execution plan is simular
with second one and execution time is about 4 seconds. I feel that
it is possible to use execution plan simular with first one,
and make outer join queries fly (as it happen
tion definition
would improve maintainability, compared with invoking createlang
as separate command.
--
Victor Wagner [EMAIL PROTECTED]
Chief Technical Officer Office:7-(095)-748-53-88
Communiware.Net Home: 7-(095)-135-46
>Victor Wagner <[EMAIL PROTECTED]> writes:
>> As far as I understand, following three queries are exactly equivalent:
>Same results, but the second two constrain the planner's choice of join
>order. See
>http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/
uld make
postgresql behavoir closer to standard SQL.
In my (user) point of view, it is obvoisly bugfix, rather than added
feature, so it has right to appear in 7.2.x release.
> because of concern about lack of testing, but seeing that we've gotten
> several complaint
t there is no backslash-command to change
working direcory. But there is such command - \cd, at least in 7.2.1
--
Victor Wagner [EMAIL PROTECTED]
Chief Technical Officer Office:7-(095)-748-53-88
Communiware.Net Home: 7-(095)-135-46-61
http://www.comm
and LC_COLLATE categories are needed.
BTW, version of postgresql in Debian woody is 7.2.1
So it is strange, that you have earilier one. Have you installed it from
Debian package or build by hand? If later, it is better to revert to
Debian version.
--
Victor Wagner