The 7.0-2 RPMset fixes the following:
1.) SPI headers are now the 7.0 set, and not the 6.5.3 set;
2.) pg_options default to NOT enable syslog, or extended query logging, as
syslogd has some issues with long queries (such as issued by psql's \d
command!);
3.) Alpha patches have returned
Bruce Momjian wrote:
>
> [CC: to general list.]
>
> > I might add that their test lists 52 features of PostgreSQL which
> > MySQL doesn't have (13 functions). It also lists 122 features of
> > MySQL which PostgreSQL doesn't have; 78 of those are extra
> > functions (40 of these, just for M$-OD
PostgreSQL 7.0 has been a huge success. Bug reports since release have
been so few that we thought our e-mail system wasn't working properly.
Turns out things are very quiet because the release is so stable.
So, those people waiting on the fence to try 7.0, go ahead. It is
ready for prime-time.
I would like to be able to say:
SELECT url,score_a(text, CAST('term' AS TEXT)) AS score FROM articles
WHERE score > 0
ORDER BY score DESC;
This returns: ERROR: Attribute 'score' not found.
The following works:
SELECT url,score_a(text, CAST('term' AS TEXT)) AS score FROM articles
WHERE score_a
Although not exactly what you were asking about, it might be easier to get
the effect with a before insert trigger written in plpgsql.
(only minimally tested -- and against a 6.5 db - and replace the 100 and 0.1
with real values)
create function checktriggerfunc() returns opaque as '
begin
if (N
From the create_rule man page this example is offered:
CREATE RULE example_5 AS
ON INERT TO emp WHERE new.salary > 5000
DO
UPDATE NEWSET SET salary = 5000;
But what is "NEWSET"? Is it a keyword?
My problem is that on an insert with an invalid amount I try t
On Fri, 19 May 2000, Matthias Urlichs wrote:
# If a table has an index (let's say it is a btree on fields a,b), and
# if a SELECT/INSERT/UPDATE/DELETE is issued with field a being either
# inserted or in the where clause, then the database needs to use that
# index. Period.
That's not th
Sascha Ziemann wrote:
>
> Hi,
>
> how should I write this:
>
> todolist=# select name from tasks_t where id = 5 and NOT done;
> ERROR: argument to NOT is type 'numeric', not 'bool'
>
> bis später...
> Sascha
SELECT name FROM tasks_t WHERE id = 5 AND done = False;
Hope that helps,
Mike Mas
