#x27;s missing on this version or I'm I doing
> something wrong on code? If is a feature missing, is already implemented
> on some version afterwards?
>
> Best regards,
> Luís Sousa
>
>
> ---(end of broadcast)---
> TIP 4: Have you searched our list archives?
>
>http://archives.postgresql.org
SETOF in pl/pythonu appeared in 8.2
--
Adrian Klaver
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
; They are completely different.
>
> Ezequias
>
Try select md5('password'||'user')
The generated hash is a combination of the password and the user name.
--
Adrian Klaver
[EMAIL PROTECTED]
---(end of broadcast)
ctions too. I am using the SQL
> tool of PgAdmin III.
>
> Any help would be glad.
>
Can we see the complete function?
--
Adrian Klaver
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
e: 42601
> > Character: 1
> > I installed the pgsql but I don't think it is a problem of language.
> > What could be wrong ? I am not using functions too. I am using the SQL
> > tool of PgAdmin III.
> >
> > Any help would be glad.
> >
> > Ezequias
&g
x27;t want to do it in
> view. Can somebody help me?
>
> Regards
> skarthi
The problem is with your use of the substr() function. You are passing it a
field of type bit (week_flag) where the function needs a text type. See the
documentation for bit functions-
http://www.postgresql.org
those " or '
> within the data? After a couple days I wasn't able to find any examples to
> help.
>
> ---(end of broadcast)---
> TIP 4: Have you searched our list archives?
>
> http://archives.po
not enough because there may be other such tables created in other sessions.
> Or maybe anyone knows the identification (apart from 'others') of error to
> trap it with EXCEPTION clause?
select * from temp_table limit 1;
Trap error 42P01 Undefined table.
--
Adrian Klaver
[EMAIL
gt; best,
> iuri
>
>
>
>
> ---(end of broadcast)---
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>choose an index scan if your joining column's datatypes do not
>
365 as age; seems messy.
> select (now()-'1987-02-01')/365; gives extraneous junk.
>
> Thanks!
SELECT age('1987-02-01'::timestamp);
age
--
20 years 11 mons 26 days
(1 row)
--
Adrian Klaver
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: explain analyze is your friend
/2006-09/msg00803.php
http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php
--
Adrian Klaver
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
ot;Reply All" to this message, I'd
> appreciate it.
>
> Sincerely, Dean
Test
--
Adrian Klaver
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ot;Reply All" to this message, I'd
> appreciate it.
>
> Sincerely, Dean
It bounced.
--
Adrian Klaver
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Monday 25 February 2008 7:32 pm, Scott Marlowe wrote:
> On Mon, Feb 25, 2008 at 9:17 PM, Adrian Klaver <[EMAIL PROTECTED]> wrote:
> > On Monday 25 February 2008 7:13 pm, Dean Gibson (DB Administrator) wrote:
> > > I have changed something in my eMail client regarding r
On Monday 25 February 2008 8:07 pm, Scott Marlowe wrote:
> On Mon, Feb 25, 2008 at 9:54 PM, Adrian Klaver <[EMAIL PROTECTED]> wrote:
> > > So, your email client puts Dean's email address back in? Might I ask
> > > what option you chose? And if you have more th
-- Forwarded Message: --
From: [EMAIL PROTECTED] (Adrian Klaver)
To: Shawn <[EMAIL PROTECTED]>
Subject: Re: [SQL] Question 2 Interval and timestamptz
Date: Wed, 26 Mar 2008 16:24:39 +
>
> -- Original message --
> From
-- Forwarded Message: --
From: [EMAIL PROTECTED] (Adrian Klaver)
To: Shawn <[EMAIL PROTECTED]>
Subject: Re: [SQL] Part 1 of several - Converting a varchar to an interval
Date: Wed, 26 Mar 2008 16:16:58 +
>
>
>
>
> --
-- Original message --
From: Tom Lane <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] (Adrian Klaver) writes:
> > select ('134987'::int/1000.00) * interval ' 1 second' ;
> > ?column?
> > --
>
-- Original message --
From: Tom Lane <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] (Adrian Klaver) writes:
> > select ('134987'::int/1000.00) * interval ' 1 second' ;
> > ?column?
> > --
>
-- Original message --
From: Tom Lane <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] (Adrian Klaver) writes:
> > Select 134987 * interval '1 msec';
> > ERROR: invalid input syntax for type interval:
Can you show the error message if any?
--
Adrian Klaver
[EMAIL PROTECTED]
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
ou found out
now() fixes the time at the start of the transaction and does not change,
clock_timestamp() does. See URL below for a more complete explanation:
http://www.postgresql.org/docs/8.2/interactive/functions-datetime.html
--
Adrian Klaver
[EMAIL PROTECTED]
--
Sent via pgsql-sql mailing l
;
>
>
> How can I solve this?
>
>
>
> Met vriendelijke groet,
>
>
>
> Paul Dam
You will need to show the actual query, but I suspect you have an extra period
in your table name. Instead of public.table_name you have something like
public.table.name.
--
Adrian Klav
mplied for the
int4,bool cast. See for more details:
http://www.postgresql.org/docs/8.3/interactive/catalog-pg-cast.html
--
Adrian Klaver
[EMAIL PROTECTED]
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
ERROR: loop variable of loop over rows must be record or row variable at or
> near "loop" at character 195
>
> ** Error **
>
> ERROR: loop variable of loop over rows must be record or row variable at or
> near "loop"
> SQL state: 42601
> Char
ger examine the row to see if it meets the criteria
for deletion. If it does RETURN a NON NULL value so the trigger completes,
otherwise RETURN NULL to prevent the DELETE.
--
Adrian Klaver
[EMAIL PROTECTED]
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
RETURN OLD;
ELSIF current_user != 'privileged_user' AND old.deduced ='t' THEN
RETURN NULL;
ELSIF current_user = 'priviliged_user' THEN
RETURN OLD
END;
$Body$
LANGUAGE plpgsql;
--
Adrian Klaver
[EMAIL PROTECTED]
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
On Friday 10 October 2008 1:57:28 pm Adrian Klaver wrote:
> On Friday 10 October 2008 11:25:05 am Christopher Maier wrote:
> > On Oct 10, 2008, at 2:05 PM, Alvaro Herrera wrote:
> > > Looks like you should revoke DELETE privilege from plain users, and
> > > have your d
cause if
> dependent rows are not deleted immediately after the row that supports
> it, then I can get "orphaned" rows left in the table that have no
> supporting rows.
>
> Thanks,
> Chris
>
Is not possible to delete the dependent rows from within the BEFORE trigger
somebody can help me
>
> Thanks in advanced!!
Take a look at:
http://www.postgresql.org/docs/8.3/interactive/sql-explain.html
and:
http://www.postgresql.org/docs/8.3/interactive/using-explain.html
--
Adrian Klaver
[EMAIL PROTECTED]
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.o
ghtmap.tif')
> ^
>
> I would appreciate a lot if you offer your input. Thanks a lot.
>
> John
--
Adrian Klaver
akla...@comcast.net
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
Oops, forgot to reply to list.
-- Forwarded Message --
Subject: Re: [SQL] Creating a function with single quotes
Date: Thursday 19 February 2009
From: Adrian Klaver
To: stay...@washoecounty.us
On Thursday 19 February 2009 7:41:11 am Shawn Tayler wrote:
> Hello,
>
>
Memo to self:
Remember hit reply all.
-- Forwarded Message --
Subject: Re: [SQL] Creating a function with single quotes
Date: Friday 20 February 2009
From: Adrian Klaver
To: "Leif B. Kristensen"
On Friday 20 February 2009 6:13:03 am you wrote:
> On Friday 20.
On Friday 20 February 2009 6:29:43 am Leif B. Kristensen wrote:
> On Friday 20. February 2009, Adrian Klaver wrote:
> >Actually you need both semicolons. One after the RETURN statement and
> > one after the END statement
> >See below for full details:
> >http://
st_function" line 5 at SQL statement
You have declared function to RETURN SETOF. In order for that to work you need
to do RETURN NEXT. See below for difference between RETURN and RETURN NEXT:
http://www.postgresql.org/docs/8.3/interactive/plpgsql-control-structures.html#PLPGSQL-CONTROL-STRUCTU
- "Peter Willis" wrote:
> Adrian Klaver wrote:
> > On Wednesday 01 April 2009 4:31:20 pm Peter Willis wrote:
> >> Hello,
> >>
> >> I am having a problem with a FUNCTION.
> >> The function creates just fine with no errors.
> >
On Thursday 02 April 2009 4:22:06 pm Peter Willis wrote:
> Adrian Klaver wrote:
> > Did you happen to catch this:
> > Note that functions using RETURN NEXT or RETURN QUERY must be called as a
> > table source in a FROM clause
> >
> > Try:
> > select * from te
is put a trigger on the table that
trims
the strings on INSERT or UPDATE.
>
>
>
> Volkmar
--
Adrian Klaver
akla...@comcast.net
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
On Thursday 02 April 2009 6:16:44 pm Adrian Klaver wrote:
>
>
> Now I remember. Its something that trips me up, the RECORD in RETURN setof
> RECORD is not the same thing as the RECORD in DECLARE RECORD. See below for
> a better explanation-
> http://www.postgresql.org/docs/8.3/i
On Friday 03 April 2009 6:51:05 am Adrian Klaver wrote:
> On Thursday 02 April 2009 6:16:44 pm Adrian Klaver wrote:
> > Now I remember. Its something that trips me up, the RECORD in RETURN
> > setof RECORD is not the same thing as the RECORD in DECLARE RECORD. See
> &g
- "Peter Willis" wrote:
> Adrian Klaver wrote:
> > On Friday 03 April 2009 6:51:05 am Adrian Klaver wrote:
> >> On Thursday 02 April 2009 6:16:44 pm Adrian Klaver wrote:
> >>> Now I remember. Its something that trips me up, the RECORD in
> RETURN
id | topic | message
+--+--
1 | My favorite food | I like lasagna!
2 | My favorite food | Pizza is also a favorite
3 | Are squares better then circles?
101 - 141 of 141 matches
Mail list logo
