> From: Tom Lane <[EMAIL PROTECTED]>
> Date: Thu, 20 Sep 2001 00:02:31 -0400
>> Perhaps my understanding of column vs table constraints is incomplete
>> but this doesn't seem to be proper behavior,
>
> Why not? A constraint is a constraint, it should be valid whenever one
> checks it.
The quest
On Wed, 19 Sep 2001, Keary Suska wrote:
> It appears that Postgres checks column CHECK constraints when performing an
> update regardless of whether the particular column is being updated. Perhaps
> my understanding of column vs table constraints is incomplete but this
> doesn't seem to be proper
Keary Suska <[EMAIL PROTECTED]> writes:
> It appears that Postgres checks column CHECK constraints when performing an
> update regardless of whether the particular column is being updated.
I believe that's true...
> Perhaps my understanding of column vs table constraints is incomplete
> but this
It appears that Postgres checks column CHECK constraints when performing an
update regardless of whether the particular column is being updated. Perhaps
my understanding of column vs table constraints is incomplete but this
doesn't seem to be proper behavior, and I can't find it documented anywher
I am advised by the (few remaining) Great Bridge folk that they will be
shutting down their webservers very shortly, like tomorrow. This will
take the project pages at greatbridge.org offline.
All the data at greatbridge.org has been transferred to a hub.org server
at http://gborg.postgresql.org
On 19 Sep 2001 [EMAIL PROTECTED] wrote:
> Hello there,
>
> Finally I got a \"yes\" and I\'m moving from Microsoft SQL Server to
> Postgresql. I\'m using PHP4 and PHPLIB to work with query
> abstractions. I have a lot of subqueries like:
>
> WHERE ... EXISTS (SELECT ...)
>
> I was researching
[EMAIL PROTECTED] writes:
> WHERE ... EXISTS (SELECT ...)
>
> I was researching and found ambiguous information about this kind of subqueries, is
>that working fine with Postgresql?
Yes.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(
Peter Bierman:
> While checking out TOT pgsql today onto an HFS+ file system
(case-preserving, case-insensitive), I hit the following CVS conflict:
>
> pgsql/src/backend/utils/mb/Unicode/utf8_to_alt.map
pgsql/src/backend/utils/mb/Unicode/utf8_to_ALT.map
>
> HFS+ can not store two differerent file
IIRC, pg_encoding_to_char relates to multi-byte support. Chances are, your
libpq.so was not originally compiled with multi-byte support. You may have
to recompile.
It may also mean that you have multiple libpq.so installations, one which
does not have multi-byte support and which is being loaded
Hello there,
Finally I got a \"yes\" and I\'m moving from Microsoft SQL Server to Postgresql. I\'m
using PHP4 and PHPLIB to work with query abstractions. I have a lot of subqueries like:
WHERE ... EXISTS (SELECT ...)
I was researching and found ambiguous information about this kind of subqueri
At 12:46 19.09.01 -0700, Roderick A. Anderson wrote:
To everyone :
> Who are you and how did you get this e-mail address? Why are you
>sending me this stuff?
Postgres mailling-list was inserted by error in my mailing and I don't know
why ?! Of course I certainly made a mistake...
All my apol
Hello !
Ok...
I wrote a small text against that virus just in case you need it !
http://www.horus.ch/virus180901.txt
A bientôt !
Denis Bucher
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscr
I´m about to change my postgres 7.1.3 to another compilation, but with
multi-byte enabled.
What kind of precuations do I have to take?
pg_dumpall and then put it back on the new database? Do I have to initdb the
database?
Saludos... :-)
--
Porqué usar una base de datos relacional cualquiera,
On Wed, 19 Sep 2001, Patrick Welche wrote:
> select coalesce(sum(deltafromoctets),0)
> from trans,stats
> where stats_id=stats.id
>and (timeslicet < '1:05' OR timeslicet > '6:05')
>
> returns a number (9188191930), whereas
>
> select coalesce(sum(deltafromoctets),0)
> from trans,stats
On Lun 17 Sep 2001 12:14, Cosmos Tong wrote:
> Dear all,
>
> I can compile PHP 4.0.6 with Postgres 7.1.3 successfully. However,
> when I try to start apache, an error comes out:
>
> Cannot load /usr/local/apache/libexec/libphp4.so into server:
> /usr/local/apache/libexec/libphp4.so: undefined sy
On Wednesday 19 September 2001 11:25, Tom Lane wrote:
> Denis Perchine <[EMAIL PROTECTED]> writes:
> > BTW, using begin; lock table; create index;drop index;commit; is not
> > working,
>
> ??
>
> regression=# create table foo (f1 text);
> CREATE
> regression=# create index fooi1 on foo(f1);
> CREA
On Wed, 19 Sep 2001, Vince Vielhaber wrote:
Hi All,
Just to let you know, the server's were up and running and were very
stable at the time of this outage. The cause was a leading router by a
provider in the Toronto area that is a few levels above where
www.postgresql.org resides. The new versi
select coalesce(sum(deltafromoctets),0)
from trans,stats
where stats_id=stats.id
and (timeslicet < '1:05' OR timeslicet > '6:05')
returns a number (9188191930), whereas
select coalesce(sum(deltafromoctets),0)
from trans,stats
where stats_id=stats.id
and (timeslicet < '1:05' OR timesl
While restoring a db I got the following messages:
CREATE UNIQUE INDEX "bookings_inventoryid_key" on "bookings" using btree (
"inventoryid" "int4_ops" )
NOTICE: RegisterShareInvalid: SI buffer overflow
CREATE INDEX "bookings_account_idx" on "bookings" using btree ( "acount"
"bpchar_ops" )
NOTICE:
> Has anyone else experienced serious performance problems when using arithmetic
> expressions in queries?
...
> a and b are numeric(10, 3)
numeric() is implemented with binary coded decimal representation, which
is substantially slower than direct processor supported math involving
just ints and
--- Doug Moore <[EMAIL PROTECTED]> wrote:
> Hi,
>
> As I understand it, in order to read in a file containing sql
> commands
> I should use the \i syntax in psql.
>
> So, from the psql prompt I type:
>
> \i /root/phones
>
> I get back "/root/phones: permission denied"
>
> I am in psql as th
Tille, Andreas writes:
> SELECT Hauptdaten_Fall.MeldeKategorie, Count(Hauptdaten_Fall.ID) AS Anz
> FROM Hauptdaten_Fall WHERE (((Hauptdaten_Fall.IstAktuell)=20)) GROUP BY
> Hauptdaten_Fall.MeldeKategorie ORDER BY Hauptdaten_Fall.MeldeKategorie;
> (which should just measure the time needed for th
Toujours dans la série "Merci Microsoft" (j'ai déjà prévenu à propos
des multiples trous de sécurité dans Outlook et Outlook express).
Cette menace est très sérieuse.
=== Forward ===
From: Denis Bucher <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Tuesday, Septembe
23 matches
Mail list logo
