Do SQL statements inside of plpgsql functions get planned upon every
execution, only when the function is first executed/defined, or something
else entirely?
For example, suppose I have a table foo and a function bar. Function bar
executes some SQL statements (select/insert/update) against table
On Sat, Apr 26, 2008 at 4:19 PM, Ivan Sergio Borgonovo
<[EMAIL PROTECTED]> wrote:
>
> With the added @ everything seemed to be OK.
No, the @ is just making php quietly swallow the postgresql errors
that are being returned. It changes nothing in operation.
> I had to refresh a second time to ge
On Friday 25 April 2008 14:56, Merlin Moncure wrote:
> On Thu, Apr 24, 2008 at 3:01 PM, Tino Wildenhain <[EMAIL PROTECTED]> wrote:
> > Merlin Moncure wrote:
> > > I think you're being a little too hard on enums here. I was actually
> > > in the anti-enum camp until it was demonstrated to me (and i
On Sat, 26 Apr 2008 23:14:07 +0200
Martijn van Oosterhout <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 26, 2008 at 10:52:12PM +0200, Ivan Sergio Borgonovo
> wrote:
> > How am I going to see if the transaction succeeded without
> > checking what happens for each statement and getting the cleanup
> > co
On Sat, Apr 26, 2008 at 10:52:12PM +0200, Ivan Sergio Borgonovo wrote:
> How am I going to see if the transaction succeeded without checking
> what happens for each statement and getting the cleanup code execute?
You basically actually check for the errors in the earlier pg_query()
calls, since th
I've a set of statements...
pg_query('begin;');
pg_query('do stuff');
pg_query('do other stuff');
if(!pg_query('commit;')) {
pg_query('rollback;');
// DO SOME CLEANUP HERE
}
if something goes wrong the statement actually get rolled back... but
the pg_query('commit;') statement a
"Vyacheslav Kalinin" <[EMAIL PROTECTED]> writes:
> Case insensitive pattern matching gives strange results for non-ascii
> character (such as UTF-8 encoded cyrillic letters):
Yeah, the regex locale support doesn't work well in multibyte character
sets --- it basically will not recognize that non-A
Hello,
Case insensitive pattern matching gives strange results for non-ascii
character (such as UTF-8 encoded cyrillic letters):
test=# select 'б' ~* 'Б' ;
?column?
--
f
(1 row)
( 'б' and 'Б' are lower and upper case variants of cyrillic 'B')
at the same time:
test=# select 'б' ilike 'Б'
Martijn van Oosterhout <[EMAIL PROTECTED]> writes:
> On Thu, Apr 24, 2008 at 06:30:27PM +1200, Steve Martin wrote:
>> => show timezone ;
>> TimeZone
>> -
>> NZST-12NZDT
>> (1 row)
> I have no idea what timezone that it. Presumably it switches between
> daylight savings and non-daylig
On Thu, Apr 24, 2008 at 05:04:38AM -0700, xaviergxf wrote:
> I had the postgresql version 8.2, but i´ve updated it to the 8.3.
> During the installation, postresql show this message "Failed to run
> initdb: 1". I already tried to remove and reinstall, but it does not
> works.
>
> Did anyone know h
On Thu, Apr 24, 2008 at 06:30:27PM +1200, Steve Martin wrote:
> Hi,
>
> We are having trouble with the output of timestamp with time zone with
> versions 8.1.10 and 8.3.1.
> It seems reversed, and change over times are incorrect.
>
> timezone for both is:
> => show timezone ;
> TimeZone
> ---
Martin Marques escribió:
I'm re-writing documentation I have used in the past to give PG courses,
and at this moment I upgrading the information in my docs to fit PG 8.3.
What I'm stuck with now is pgiomonitor, which seems to not work due to
the changes that happened between 8.1 (last time I u
I'm re-writing documentation I have used in the past to give PG courses,
and at this moment I upgrading the information in my docs to fit PG 8.3.
What I'm stuck with now is pgiomonitor, which seems to not work due to
the changes that happened between 8.1 (last time I used it) and 8.3.
Does an
Hi,
We are having trouble with the output of timestamp with time zone with
versions 8.1.10 and 8.3.1.
It seems reversed, and change over times are incorrect.
timezone for both is:
=> show timezone ;
TimeZone
-
NZST-12NZDT
(1 row)
Note, change over times for this year is:
Sun
Hi,
I had the postgresql version 8.2, but i´ve updated it to the 8.3.
During the installation, postresql show this message "Failed to run
initdb: 1". I already tried to remove and reinstall, but it does not
works.
Did anyone know how can i solve this problem?
Thanks
--
Sent via pgsql-general m
hi, i haven´t found the explication about my problem...
On 24 abr, 03:04, [EMAIL PROTECTED] (Klint Gore) wrote:
> xaviergxf wrote:
> > Hi,
>
> > I´m trying to do the follow: create a table like:
> > create table t(
> > cod serial,
> > data_type char(10),
> > value ???
> > );
>
> > I woul
16 matches
Mail list logo
