Tom Lane wrote:
>
> "Tim Dunnington" <[EMAIL PROTECTED]> writes:
> > If you create a function with a table as the argument, and later alter that
> > table and add a new column, the function fails saying "incorrect number of
> > attributes for table _tablename_" Dropping and readding the function
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> cascade=> select cash_out(2);
>> pqReadData() -- backend closed the channel unexpectedly.
> I can confirm this is crashes in 7.1 too.
You can get this sort of result with almost any input or output function
:-(. The problem is that they're mostly mis
Christian HUGUES ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
pqReadData() -- backend closed the channel unexpectedly
Long Description
I've installed the PostgreSQL 7.0.3 on a RedHat 6.1, everything was well during
installa
Stephan Szabo <[EMAIL PROTECTED]> writes:
>> In fact, there's a good argument that we should require the two columns
>> to have the exact same datatype.
> I think the spec only requires them to be comparable
Oh, in that case never mind ... but I'd still favor checking for
existence of the compar
I remember that you cannot open more than 16 sessiones at same time
by default, if more than that you have to reset, I believe you can
find how from documentation.
Jie LIANG
Internet Products Inc.
10350 Science Center Drive
Suite 100, San Diego, CA 92121
Office:(858)320-4873
[EMAIL PROTECTE
On Tue, 12 Dec 2000, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> >> In fact, there's a good argument that we should require the two columns
> >> to have the exact same datatype.
>
> > I think the spec only requires them to be comparable
>
> Oh, in that case never mind ... but
"Tim Dunnington" <[EMAIL PROTECTED]> writes:
> If you create a function with a table as the argument, and later alter that
> table and add a new column, the function fails saying "incorrect number of
> attributes for table _tablename_" Dropping and readding the function does
> not fix this pro
Added to TODO:
* SELECT cash_out(2) crashes because of opaque
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> cascade=> select cash_out(2);
> >> pqReadData() -- backend closed the channel unexpectedly.
>
> > I can confirm this is crashes in 7.1 too.
>
> You can get this sort of resul
On Tue, 12 Dec 2000, Tom Lane wrote:
> Stephan Szabo <[EMAIL PROTECTED]> writes:
> >> 2) It should be error in *creation* of table if there is no comparasion
> >> operator for constrain check
>
> > Possibly, although it currently doesn't to allow you to add the operator
> > after you do the ref
Merrill Oveson <[EMAIL PROTECTED]> writes:
> This doesn't:
> select distinct
> orgid,
> case when status = 'y' then '1' else '0' end
> from vend
Try
select distinct
orgid,
case when status = 'y' then '1'::text else '0'::text end
Stephan Szabo <[EMAIL PROTECTED]> writes:
>> 2) It should be error in *creation* of table if there is no comparasion
>> operator for constrain check
> Possibly, although it currently doesn't to allow you to add the operator
> after you do the references. The benefits of that might be outweighed
This works:
select
orgid,
case when status = 'y' then '1' else '0' end
from vend
This doesn't:
select distinct
orgid,
case when status = 'y' then '1' else '0' end
from vend
The only difference is the absence of dis
Mike McDonough ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Solaris ODBC - linker flag needs to be set when building shared objects
Long Description
Linker flag which needs to be set when building shared objects to prevent a
> Hi.
>
> I use version from cvs.
>
> I want to have array of referencies to another table, so I do:
> cms=# create table a (a int primary key); create table b (b int[]
> references a);
> NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'a_pkey' for
> table 'a'
> CREATE
> NOTICE:
PostgreSQL 7.1 will have pygresql 3.1.
[ Charset ISO-8859-2 unsupported, converting... ]
> Hi,
>
> in PostgreSQL 7.0.3 is still PyGreSQL 2.4
> that version is very old, current version is 3.1
>
> can you include the new version? PygreSQL 3.1
> is Python DB-API 2.0 compliant, and it's a big
> ad
I can confirm this is crashes in 7.1 too.
>
> Hello,
>
> I was just experimenting, trying to see if I could find a function that
> would format a numeric value like 'money' with Postgres 7.0.2. Here's
> what happened:
>
> ##
> cascade=> select cash_out(2);
> pqReadData() -- backend closed
After installing:
PostgreSQL version 7
and after starting:
postmaster -D {in task 2}
on a: RedHat 6.2
Linux server
running 486, 32MB
RAM
attempting to issue:
createbd testdb {in task 1}
as user:
postgres
I get the following
message:
/usr/bin/psql: error
in loading shared libraries: /us
Hi.
I use version from cvs.
I want to have array of referencies to another table, so I do:
cms=# create table a (a int primary key); create table b (b int[]
references a);
NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index 'a_pkey' for
table 'a'
CREATE
NOTICE: CREATE TABLE will create
Hello,
I was just experimenting, trying to see if I could find a function that
would format a numeric value like 'money' with Postgres 7.0.2. Here's
what happened:
##
cascade=> select cash_out(2);
pqReadData() -- backend closed the channel unexpectedly.
This probably means the back
Dear sir,
we are finding it difficult to connect to
postgresql database using the postgresql driver i.e.
using jdbc connectivity..trying it on apache web
server on linux
otherwise in ordinary applications it is working fine.
Could u plz suggest us a remedy as soon as possible..
thanking
Hi,
in PostgreSQL 7.0.3 is still PyGreSQL 2.4
that version is very old, current version is 3.1
can you include the new version? PygreSQL 3.1
is Python DB-API 2.0 compliant, and it's a big
advantage over 2.4
thanks,
Miroslav Vasko
I have created a table with a DATETIME column:
create table registereduser
(
...
registeredDate DATETIME NOT NULL
)
I inserted a new record into this table, with the registeredDate = new
Timestamp(new Date().getTime()))
On retrieving this record, the following stack trace ensued:
Exce
I think that I've found a little bug in the 7.1beta1 JDBC drivers.
Attached is a simple test case which produces the problem on my setup
(LinuxPPC 2000, on Apple PowerMac G3-400Mhz, 512MB). It would seem that
the drivers and/or the DBMS has a problem with nested queries, even
simple ones.
Here's
Strange, this works:
select * from users where last_visit > now() + 7;
-- last_visit is nullable, of type timestamp
But this doesn't
select * from users where last_visit + 7 > now();
ERROR: Unable to convert null timestamp to date
-- yes, there are users where last_visit IS NULL
BTW
PostgreSQL 7.0.3 continues freezing after restoring a table with 60.000 rows
after about 8.000 rows.
920 pts/0S 0:00 psql -d database -f temp_registration.dump
922 ?D 0:08 /usr/bin/postgres localhost pguser database
commit
976 ?S 0:00 /usr/bin/postgres loc
Quoting najeeb ahmed <[EMAIL PROTECTED]>:
>
>
>
> this is to inquire whether postgresql provides the
> source code of jdbc drivers(any type).if so please let
> me know the url as soon as possible.
>
> as i need to customize it to suite my organizations
> requirements
The sources are in
this is to inquire whether postgresql provides the
source code of jdbc drivers(any type).if so please let
me know the url as soon as possible.
as i need to customize it to suite my organizations
requirements
THANKS
CHEER
Synopsis:
If you create a table with a foreign key reference, and later change the name
of the referenced field in the referenced table, subsequent updates on the
given table will result in an error that the old field name does not exist.
I've also seen the corollary to this, where an update
NOTE: Please retract similar, earlier entry (hit send by mistake :-)
Synopsis:
If you create a function with a table as the argument, and later alter that
table and add a new column, the function fails saying "incorrect number of
attributes for table _tablename_" Dropping and readding the f
> Short Description
> foreign key check makes a big LOCK
>
> Long Description
> in: src/backend/utils/adt/ri_triggers.c
>
> RI_FKey_check(), RI_FKey_noaction_upd(), RI_FKey_noaction_del(), etc..
> checking the referential with SELECT FOR UPDATE.
>
> After BEGIN TRANSACTION: the INSERT/DELETE/UP
30 matches
Mail list logo
