Skip site navigation (1) Skip section navigation (2)

Re: update functions locking tables

From: Clodoaldo Pinto <clodoaldo(dot)pinto(at)gmail(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>,"pgsql-general postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: update functions locking tables
Date: 2005-08-31 01:16:58
Message-ID: a595de7a05083018163bdb827c@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
2005/8/30, Jim C. Nasby <jnasby(at)pervasive(dot)com>:
> 
> FWIW, that where clause might be more efficient as
> WHERE pontos_0 > pontos_7. Some databases would be able to use indexes
> to answer that (not sure if PostgreSQL could), plus it removes an
> operator. It also seems to be cleaner code to me. :)
> --

Done, thanks.

Regards, Clodoaldo Pinto

In response to

pgsql-general by date

Next:From: Michael FuhrDate: 2005-08-31 02:38:59
Subject: Re: PQConnectdb SSL (sslmode): Is this a bug
Previous:From: Jim C. NasbyDate: 2005-08-30 23:47:04
Subject: Re: update functions locking tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group