hello.
what are perfomance difference bitween
a) update t1 set f1 = 'x', f2 = 'y';
b) update t1 set f1 = 'x', f2 = f2;
c) update t1 set f1 = 'x';
?
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if yo
On Thu, 18 Mar 2004, Raman wrote:
> In my query of time zone i have details of interval with me like '-9:00',
> '+5:30' etc
>
> my problem is regarding the format of Date which i receive... ie. when I add
> the interval field the results are like:
> Query:
> select current_date at TIME ZONE "inter
Hello All...
In my query of time zone i have details of interval with me like '-9:00',
'+5:30' etc
my problem is regarding the format of Date which i receive... ie. when I add
the interval field the results are like:
Query:
select current_date at TIME ZONE "interval" '+5:30';
timezone
David Olbersen wrote:
> *sigh* I'd rather have pilot error than having to wait for a patch :)
Hmmm, that doesn't look right in retrospect. What I meant to say was
THANK YOU TOM!
--
David Olbersen
iGuard Engineer
St. Bernard Software
15015 Avenue of Sciences
San Diego, CA 92127
x2152
-
Tom Lane wrote:
> Hate to tell you this, but it's just pilot error. You've got comments
> like these embedded in the plpgsql function:
>
> ELSIF cat = ''none'' THEN
> -- none,none = don't show the languages, or categories
> (whaaat?) FOR result IN
>
>
Tom Lane wrote:
> Hmm ... plpgsql had some string-length issues as recently as 7.2.2, but
> I don't know of any problems since then. Could you submit a *complete*
> test case, rather than making us guess the details?
Sure. I didn't want to dump a huge email to have somebody say "Addressed in 7.3
On Tuesday 16 March 2004 5:56 pm, Frank Finner wrote:
> On Tue, 16 Mar 2004 16:54:18 + Gary Stainburn
> <[EMAIL PROTECTED]> sat down, thought
>
> long and then wrote:
> > Hi folks.
> >
> > I've got a last_updated field on my stock records of type timestamp.
> >
> > This last_updated field I get
On Wednesday 17 March 2004 00:47, David Olbersen wrote:
>
> Here's the "clean" code that doesn't work:
>
> FOR result IN
> SELECT
> initcap( c.name ) AS category,
> initcap( l.language ) AS language,
>
