=?iso-8859-1?q?Mart=EDn=20Marqu=E9s?= <[EMAIL PROTECTED]> writes:
> Which is the best approach to put in a check constraint
> col <> something
> col != something
> ?
There's really no difference ... although <> is the
SQL-standard-approved spelling, if that matters to you.
I downloaded the latest version from Sun's site, Java 2 SDK EE 1.2.1.
Tim
- Original Message -
From: "Joseph Shraibman" <[EMAIL PROTECTED]>
To: "Tim Barnard" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, May 07, 2001 5:59 PM
Subject: Re: [GENERAL] A different compile problem
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Fran Fabrizio writes:
>> What's the best way to alter a column definition after the fact (i.e.
>> int8-->int4). Is the answer dump, drop table, make new table with new
>> definition and same name, import data?
> Yes.
Dump and reload can be avoided
Hi,
Chris Smith wrote:
>
> Hi,
>
> Did you try what it suggests?
>
> If you're sure PostgreSQL isn't already running, remove the
> "/tmp/.s.PGSQL.5432" file, and try again.
That file didn't exist...;-)
--
/) John Clark Naldoza y Lopez (\
/ )Software De
Hi,
Did you try what it suggests?
If you're sure PostgreSQL isn't already running, remove the
"/tmp/.s.PGSQL.5432" file, and try again.
> I recently came across a problem wherein I am not able to start my
> postgreSQL 7.0.3 server.
>
> Here's what happens..;-(
>
> postgres@kahoy /root$ postmas
If you are sure that no other postmaster is running, try deleting the file
/tmp/.s.PGSQL.5432, as the error message suggests. When you've done that,
you should be able to start the postmaster.
Poul L. Christiansen
On Tue, 8 May 2001, John Clark L. Naldoza wrote:
> Hi,
>
>
> I recently came
On Thu, 3 May 2001 23:03:57 +0100, Simon Crute wrote:
> [simon@sunshine DBD-Pg-0.98]$ make test
> PERL_DL_NONLAZY=1
> /usr/bin/perl -Iblib/arch -Iblib/lib -I/usr/local/lib/perl5/5.6.0/i686-linux
> -I/usr/local/lib/perl5/5.6.0 test.pl
> OS: linux
> Use of uninitialized value in join at test.pl lin
Hi John,
What OS are you running it on?
For example, I've been told that Debian Linux puts its socket files in
/var/run/postgresql instead of /tmp/.
The idea here, is to find that socket file and remove it. For most
OS's, it's in /tmp/ but for yours it might not be, especially if you've
instal
