On Fri, Dec 31, 2004 at 15:02:56 -0600,
[EMAIL PROTECTED] wrote:
>
> I've put an '*' next to the rows I want. So my dilemma is two part.
> First, I want to sort by the ordinal information only when the arc is
> pointing from the source object (id 638) to the other objects. Well, it's
> pretty
> Define the problem, not how you think it should be solved. What
> are you trying to do? If you can't get the query to work, then
> please post SQL statements to create and populate a table and
> describe the query results you'd like to see.
the situation is i have a set of records in a table (
Look in the configuration file and see if anything looks strange; in
particular, look for "ksqo" and see what it might be complaining about.
Regards,
Jeff
On Thu, 2004-12-30 at 16:26 -0500, Prasad Duggineni wrote:
> I do see the following error in /var/log/messages when I try to start
>
Scott Marlowe <[EMAIL PROTECTED]> writes:
> I'm certainly willing to do the vast majority of the work. As Greg I
> think mentioned, maybe a fresh start using the information_schema would
> make sense as a sort of non-pg specific backup tool or something.
This is a dead end.
First, the informatio
Derik Barclay <[EMAIL PROTECTED]> writes:
> On December 30, 2004 11:03 pm, Tom Lane wrote:
>> If you have any indexes or views referencing this column, then it's a
>> bit harder. But for the table itself I believe that will work.
> It is combined with another field to form an index.
> Does that m
On Fri, 31 Dec 2004 [EMAIL PROTECTED] wrote:
> It has come up several times on the various postgresql lists that in order
> to get around the requirement of DISTINCT ON parameters matching the first
> ORDER BY parameters, wrap the distinct query in a new 'order by' query:
>
> select * from (selec
Frank D. Engel, Jr. wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd advise use of BYTEA as well. It's much simpler to work with than
the OIDs, and has simpler semantics. You do need to escape data
before handing it to the query string, and handle escaped results (see
the docs), but ov
On Fri, Dec 31, 2004 at 10:48:21AM -0600, [EMAIL PROTECTED] wrote:
> It has come up several times on the various postgresql lists that in order
> to get around the requirement of DISTINCT ON parameters matching the first
> ORDER BY parameters, wrap the distinct query in a new 'order by' query:
>
It has come up several times on the various postgresql lists that in order
to get around the requirement of DISTINCT ON parameters matching the first
ORDER BY parameters, wrap the distinct query in a new 'order by' query:
select * from (select distinct on (a) a,b,c from foo order by a) order by c
--- ramesh phule <[EMAIL PROTECTED]> escribió:
>Dear Sir ,
>
>Can u send me one example of Functions which
> returns more than one row.
>
> Also , Wish you Happy New Year.
>
Remember this is valid code only in 7.4 and later. you
have to change to a newer version to do this.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd advise use of BYTEA as well. It's much simpler to work with than
the OIDs, and has simpler semantics. You do need to escape data before
handing it to the query string, and handle escaped results (see the
docs), but overall much nicer than worki
Is your authentication set to "Trust" in the config files ?
On Fri, 31 Dec 2004 08:45:34 -0600, Eric Scott <[EMAIL PROTECTED]>
wrote:
Heya;
I have PostGreSQL 7.3.4 on Mandrake Linux 9.2. For some reason Webmin,
when I tell it to change the password of a pgsql user, acts like it's
workin
Heya;
I have PostGreSQL 7.3.4 on Mandrake Linux 9.2. For some reason Webmin,
when I tell it to change the password of a pgsql user, acts like it's
working, but still leaves "requires password" set to "no." I've tried
running psql and executing "ALTER USER [username] WITH PASSWORD
'[password]'
It is combined with another field to form an index.
Does that mean a re-indexing will be required? or are there other issues?
On December 30, 2004 11:03 pm, Tom Lane wrote:
> Derik Barclay <[EMAIL PROTECTED]> writes:
> > Specificaly I am looking at executing something like this:
> > UPDATE pg_attr
--- Mike Cox <[EMAIL PROTECTED]> escreveu:
> Am I the only one who has trouble reading the website? Some of the
> fonts are way too small, especially the " Mirrors | Donate | Contact"
> set.
Here with Linux/FireFox and a 19" monitor at 1280x960 the fonts sizes are
adequate.
> The other problem
Hello,
You can use arrays in PL/pgSQL without problems. But You need first
init array on not NULL value.
CREATE OR REPLACE FUNCTION foo(int) RETURNS int AS $$
DECLARE x int[] = '{}';
BEGIN x[1] := $1;
RETURN x[1];
END; $$ LANGUAGE plpgsql;
regards
Pavel
> Hi all
>
> Is it possible to use a
Hi all
Is it possible to use an array of variables in a
PL/pgSQL function?
Here is a trivial example of what I am trying to
do.
create or replace
function fmfunc(int) returns int as ' declare
_int alias for $1; _ints int[3];
begin _ints[1] = _int * 2
Many thanks for your explanation.
I found in the contrib the function moddatetime
CREATE TRIGGER dmodtar_upd
BEFORE UPDATE ON tarifs
FOR EACH ROW
EXECUTE PROCEDURE public.moddatetime(dmodtar) ;
So all works fine !
PostgreSQL 8 is great.
- Original Message -
From: "Pierre-Frédéric Cai
18 matches
Mail list logo
