Re:

From: "Morten W(dot) Petersen" <morten(at)src(dot)no>
To: Vince Vielhaber <vev(at)michvhf(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re:
Date: 2000-08-07 11:45:30
Message-ID: Pine.LNX.4.21.0008071337510.2226-100000@lade.src.no
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> It'll help if you provide more info, like what version of PostgreSQL,
> what OS and version, example queries, etc..

Woop. The database that's working is a PostgreSQL 6.5 on Debian 2.1, the
database that isn't is a PostgreSQL 6.5 on Suse 6.4, both x86 architecture
machines.

The PostgreSQL on the Suse box is a standard package, the PostgreSQL on
the Debian box is compiled from scratch.

An example of a query is "SELECT id FROM inmail WHERE mailsetup_id = 1".
This is through the Python database adapter. I think I've maybe found the
problem, the database adapter on the machine that is working is at 3.0,
while the one that isn't is at 3.0 beta. Hmm. Anyways, if you guys have
any ideas I'd appreciate to hear about them.

-Morten

In response to

  • Re: at 2000-08-07 10:42:57 from Vince Vielhaber

Responses

  • Re: at 2000-08-07 12:52:37 from Morten W. Petersen

Browse pgsql-general by date

  From Date Subject
Next Message Alex Bolenok 2000-08-07 11:55:47 UNICODE output to frontend
Previous Message Simon Brooke 2000-08-07 11:35:56 Auto-increment datatypes and JDBC