The following bug has been logged online:
Bug reference: 3542
Logged by: Jens Schicke
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: GNU/Linux
Description:Dropped and recreated columns have problems with NOT
NULL contraints
Details:
piz
The following bug has been logged online:
Bug reference: 3543
Logged by: Jens Schicke
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: GNU/Linux
Description:ARRAY(SELECT ...) contruct yields NULL without rows
Details:
SELECT ARRAY(SELECT
What did you expect?
Jens Schicke wrote:
> pizza_de=# alter table store_flags add column flag integer;
> ALTER TABLE
> pizza_de=# alter table store_flags drop column flag;
> ALTER TABLE
> pizza_de=# alter table store_flags add column flag integer not null;
> ERROR: column "flag" contains null
On Thu, Aug 16, 2007 at 11:11:49AM +, Jens Schicke wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3543
> Logged by: Jens Schicke
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.4
> Operating system: GNU/Linux
> Description:ARR
Decibel! <[EMAIL PROTECTED]> writes:
> On Thu, Aug 16, 2007 at 11:11:49AM +, Jens Schicke wrote:
>> SELECT ARRAY(SELECT 1 WHERE 1 = 0) IS NULL; -- true
> And just what would you have it return? An array with no elements is by
> definition NULL.
No, there is a difference:
regression=# select
On Thu, 16 Aug 2007, Jens Schicke wrote:
> The following bug has been logged online:
>
> Bug reference: 3542
> Logged by: Jens Schicke
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.4
> Operating system: GNU/Linux
> Description:Dropped and recreated colu
The following bug has been logged online:
Bug reference: 3544
Logged by: Scott Harper
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.9
Operating system: Debian Linux (2.6.18-4-486)
Description:SQLException from JDBC driver
Details:
I have installed Postgre
Scott Harper wrote:
> When the servlet makes the DriverManager.getConnection() call, the following
> exception is thrown:
>
> org.postgresql.util.PSQLException: Something unusual has occured to cause
> the driver to fail. Please report this exception.
Can you get the full stack trace?
--
Heik
"Peter Koczan" <[EMAIL PROTECTED]> writes:
> For instance, I can open up two connections on my test server and
> illustrate the problem.
Well, the fact that psql acts that way is not unexpected, because it
doesn't monitor the database connection constantly --- when it's waiting
for console input,
