Hi Steven,
you may use COALESCE. This function should have the same behaviour as
Oracle's nvl. For documentation look at
http://www.postgresql.org/idocs/index.php?functions-conditional.html
Andre
"Steven Dahlin" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
9qj13u$2v5l$[EMAIL PROTECTED]">news:9q
Tom, Folks:
I am having a rather interesting time getting performance out of my
database. I'd really appreciate some feedback from the list on this.
As you may recall, I've gotten around Postgres' lack of rowset-returning
stored procedures by constructing "pointer tables" which simply hold
lis
Christopher Sawtell <[EMAIL PROTECTED]> writes:
> On Tue, 16 Oct 2001 03:46, Tom Lane wrote:
>> You can't. This is one of the many deficiencies of large objects.
> But now that the limit on row length / size has gone away, and that the new
> BYTEA type has appeared, it would seem that the need
I would really like a feature :)
I do not know whether it is part of the SQL standard.
Variables...
e.g.
CREATE VARIABLE foobar INTEGER DEFAULT 1 NOT NULL;
SELECT * FROM thebar WHERE id = foobar;
CREATE TEMPORARY VARIABLE...
CREATE CONSTANT
Basically all the functionality from the tabl
Your update trigger is fired FOR EACH ROW and no rows are updated i.e. no trigger
fired!
On Tue, 16 Oct 2001 14:48:59 +0200, Reiner Dassing <[EMAIL PROTECTED]> wrote:
> Hallo!
>
> I have written a very small test procedure to show a possible error
> on PostgreSQL V7.1.1.
> A trigger does not fi
Reiner Dassing <[EMAIL PROTECTED]> writes:
> I have written a very small test procedure to show a possible error
> on PostgreSQL V7.1.1.
The error is yours: you set up the trigger function to return NULL,
which means it's telling the system not to allow the INSERT or UPDATE.
> INSERT INTO test V
On Tue, 16 Oct 2001, CoL wrote:
> ---
> The 2 table query, where prog_data has ~8800 rowsn and index on prog_id:
> bash-2.04$ time echo "explain select distinct
> prog_id,prog_ftype,prog_fcasthour,prog_date from prog_dgy_xy,prog_data
> where pxygy_pid=prog_id " | psql -U
On Mon, 15 Oct 2001, Szabo Zoltan wrote:
> Hi,
>
> I have that:
>
> 1)
> db=> explain select pxygy_pid from prog_dgy_xy where pxygy_pid=12121;
> NOTICE: QUERY PLAN:
>
> Group (cost=0.00..29970.34 rows=921 width=4)
>-> Index Scan using progdgyxy_idx2 on prog_dgy_xy
> (cost=0.00..29947.3
On Tue, 16 Oct 2001 03:46, Tom Lane wrote:
> "Aasmund Midttun Godal" <[EMAIL PROTECTED]> writes:
> > How can I restrict access to large objects.
>
> You can't. This is one of the many deficiencies of large objects.
But now that the limit on row length / size has gone away, and that the new
BYTE
Bruce Momjian writes:
> TEXT limit is 1GB, as shown on the 'limits' FAQ item. Is it worth
> mentioning here? CHAR()/VARCHAR() also 1GB limit.
It is already mentioned there.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadc
> The result is as follows:
> INSERT INTO test VALUES(1,'2000-10-11 12:00:00',-20.2);
> NOTICE: Fired INSERT
> INSERT 0 0
> UPDATE test SET value = 1000.0 WHERE epoch = '2000-10-11 12:10:00' AND
> sensor_id = 1;
> UPDATE 0
>
> The insert notice can be shown!
> The update notice is not there!
>
I want to store a long article in the Postgresql in Linux, how can I put the
content into it and withdraw it back to show? urgent. Thanks.
I use JSP.
I note that all database systems are very dull in BLOB, but we need it to
make a good system. At least, the documentation/faq should have much on it
I want to store a long article in the Postgresql in Linux, how can I put the
content into it and redraw it back to show? urgent. Thanks.
I use JSP.
I note that all database systems are very dull in BLOB. Why?
Frank Zhu.
---(end of broadcast)---
T
Perhaps 'limits' should be part of FAQ, not separate entity?
Also a reference (or link) to 'limits' from other sections such as
mentioned below may be more appropriate than duplicating the information.
Frank
At 08:56 AM 10/16/01 -0400, you wrote:
>> > "BM" == Bruce Momjian <[EMAIL PROTECTED
On Monday 15 October 2001 16:12 pm, Tom Lane wrote:
> Stuart Grimshaw <[EMAIL PROTECTED]> writes:
> > SELECT a.category, b.headline, b.added, c.friendlyname
> > FROM caturljoin as a
> > INNER JOIN stories as b ON (a.url = b.source)
> > INNER JOIN urllist as c ON (a.url = d.urn)
> >
Try: ::text
CoL
guard wrote:
> thanks
>
> I have run "select substr('hi there', 3, 5)::varchar(5) as xx;"
> but get error message
> Error: ERROR: parser: parse error at or near ":"
>
> --
>
> "Lee Harr" <[EMAIL PROTECTED]> ¼¶¼g©ó¶l¥ó·s»D
> :9qd0j0$1gc3$[EMAIL PROTECTED]
>
>>>how to
>>>sele
On Mon, 15 Oct 2001 09:56:26 +0800, guard <[EMAIL PROTECTED]> wrote:
> thanks
>
> I have run "select substr('hi there', 3, 5)::varchar(5) as xx;"
> but get error message
> Error: ERROR: parser: parse error at or near ":"
>
Works for me on 7.1.2 and pre-7.2
What version are you using?
select v
Hi,
I have that:
1)
db=> explain select pxygy_pid from prog_dgy_xy where pxygy_pid=12121;
NOTICE: QUERY PLAN:
Group (cost=0.00..29970.34 rows=921 width=4)
-> Index Scan using progdgyxy_idx2 on prog_dgy_xy
(cost=0.00..29947.32 rows=9210 width=4)
than:
2)
db=> explain select pxygy_pid fro
Hallo!
I have written a very small test procedure to show a possible error
on PostgreSQL V7.1.1.
A trigger does not fire the function on update but on inserts.
Does someone have made the same experiences?
Here is the short example which is doing nothing important, just showing
the
situation:
D
This may look familiar to you - it was on the list last month.
Consider the following table
create table partitur
(userid text, val integer, ts timestamp DEFAULT NOW() );
Do some inserts
insert into partitur values('Bart', 1440);
insert into partitur values('Lisa', 1024);
insert into partitur
There is a limits FAQ item, not a separate limits FAQ. Sorry for the
confusion.
> Perhaps 'limits' should be part of FAQ, not separate entity?
>
> Also a reference (or link) to 'limits' from other sections such as
> mentioned below may be more appropriate than duplicating the information.
>
>
> "BM" == Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Could you add the length limitation for TEXT to the reference manual?
>> I searched high and low for that limit, but never found it. Also,
>> what's the max VARCHAR() or CHAR() I can create? Is that also 1Gb?
BM> TEXT limit is 1GB, as
> > "BM" == Bruce Momjian <[EMAIL PROTECTED]> writes:
>
> BM> CHAR() is best when storing strings that are usually the
> BM> same length. VARCHAR() is best when storing variable-length strings,
> BM> but you want to limit how long a string can be. TEXT is for strings
> BM> o
"Josh Berkus" wrote:
>Folks,
>
>Can anybody tell me the syntax for sending the result of an EXECUTE to a
>variable within a PL/pgSQL function again? Jan Wieck posted it to the
>list this summer, but the "searchable list archives" are bogging down.
FOR variable IN EXECUTE ''SELECT ...''
"Michael Richards" <[EMAIL PROTECTED]> writes:
> I've been watching for this for some time. First it was 7.0, then
> 7.1. Does anyone have any idea on when the row re-use code will be
> ready?
VACUUM isn't disappearing any time soon, but 7.2's version of vacuum
runs in parallel with normal tra
Tom,
> Um ... does that work? I thought LIMIT was fairly restrictive about
> what it would take as a parameter --- like, constants or $n
> parameters
> only.
>
> I do not know of any median-finding algorithm that doesn't require a
> depressingly large amount of storage...
Me neither. You're r
26 matches
Mail list logo
