2008/7/14 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> 2008/7/14 Tom Lane <[EMAIL PROTECTED]>:
>>> Are you intending to change this right now and resubmit, or is it
>>> work for later?
>
>> I prefer
2008/7/14 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> sample: select mleast(variadic array[1,2,3,4,5]);
>
> Note this would also address Jeff's complaint about not being able to
> pass zero variadic parame
2008/7/14 Florian G. Pflug <[EMAIL PROTECTED]>:
> Pavel Stehule wrote:
>>>
>>> One issue that just occurred to me: what if a variadic function wants to
>>> turn around and call another variadic function, passing the same array
>>> argument on to the
2008/7/13 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> 2008/7/13 Jeff Davis <[EMAIL PROTECTED]>:
>>> Also, it doesn't seem to allow calls to a variadic function with zero
>>> arguments, e.g. "mlea
the solutions are pretty ugly (sprintf
> vs vsprintf for instance). Can we do any better? At least in the
> polymorphic case, I'm not sure we can :-(.
>
> regards, tom lane
>
maybe with some flag like PARAMS?
SELECT least(PARAMS ARRAY[1,2,3,4,5,6]
2008/7/13 Jeff Davis <[EMAIL PROTECTED]>:
> On Sun, 2008-07-13 at 07:52 +0200, Pavel Stehule wrote:
>> you checked second or third variant? There are two variants still.
>
> Sorry for being unclear. Those comments regarded patch v2.2.1. The bug
> is in pg_function_is_visib
2008/7/13 Jeff Davis <[EMAIL PROTECTED]>:
> On Tue, 2008-06-24 at 17:10 +0200, Pavel Stehule wrote:
>> Hello
>>
>> this version implements syntax based on argmodes.
>>
>>
>> CREATE FUNCTION mleast(variadic numeric[]) RETURNS numeric AS $$
>> S
Hello
2008/7/13 Jeff Davis <[EMAIL PROTECTED]>:
> On Thu, 2008-06-26 at 17:03 +0200, Pavel Stehule wrote:
>> this is third variant with variadic argumen as scalar. But I still
>> strongly prefer second variant with conformance declared variadic
>> array with used arr
2008/7/10 Marko Kreen <[EMAIL PROTECTED]>:
> On 7/10/08, Pavel Stehule <[EMAIL PROTECTED]> wrote:
>> I am sending actualized patch
>>
>> Regards
>> Pavel Stehule
>>
>> 2008/7/9 Pavel Stehule <[EMAIL PROTECTED]>:
>>
>> &g
Hello,
I am sending actualized patch
Regards
Pavel Stehule
2008/7/9 Pavel Stehule <[EMAIL PROTECTED]>:
> 2008/7/9 Marko Kreen <[EMAIL PROTECTED]>:
>> Generally, the patch looks fine. There are few issues still:
>>
>> - plpgsql: the result columns _do_ creat
2008/7/4 Simon Riggs <[EMAIL PROTECTED]>:
>
> On Mon, 2008-06-23 at 15:13 +0200, Pavel Stehule wrote:
>
>> this patch enhance current syntax of CREATE FUNCTION statement. It
>> allows creating functions with variable number of arguments. This
>> version is d
2008/6/25 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>>> Tom Lane wrote:
>>>> Your point about the syntax is good though. It would be better if
>>>> the syntax were like
>>>> create functio
2008/6/25 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>>> Tom Lane wrote:
>>>> Your point about the syntax is good though. It would be better if
>>>> the syntax were like
>>>> create functio
2008/6/25 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>>> Tom Lane wrote:
>>>> Your point about the syntax is good though. It would be better if
>>>> the syntax were like
>>>> create functio
2008/6/25 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>>> Tom Lane wrote:
>>>> Your point about the syntax is good though. It would be better if
>>>> the syntax were like
>>>> create functio
2008/6/25 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>>> Tom Lane wrote:
>>>> Your point about the syntax is good though. It would be better if
>>>> the syntax were like
>>>> create functio
Hello
this version implements syntax based on argmodes.
CREATE FUNCTION mleast(variadic numeric[]) RETURNS numeric AS $$
SELECT min($1[i])
FROM generate_subscripts($1,1) g(i);
$$ LANGUAGE SQL;
Regards
Pavel Stehule
2008/6/24 Tom Lane <[EMAIL PROTECTED]>:
> Andrew Dunsta
or replace function decode(s_value anyelement1, variadic
(s_value anyalement1, o_value anyelement)[])
returns anyelement as $$
select ($2[i]).o_value
from generate_subcripts($1,1) g(i)
where ($2[i]).s_value = $1;
$$ language sql;
regards
Pavel Stehule
>
>regards, tom lane
>
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
2008/6/23 Andrew Dunstan <[EMAIL PROTECTED]>:
>
>
> And what about a function that takes 2 arrays as arguments?
only last argument is evaluated as variadic
so function
create or replace function foo(a int[], b int[]) ... variadic
is called
select foo(array[1,2,3], 1,2,3,4,5,6)
>
> This propos
r have to be
array. It's more consistent with following procedure implementation -
inside procedures is really array.
sample:
CREATE OR REPLACE least(varidic values numeric[]) --< ARRAY
RETURNS numeric AS $$
SELECT $1[i] --< ARRAY
FROM
Regards
Pavel Stehule
p.s. with one exception &quo
2008/6/10 Neil Conway <[EMAIL PROTECTED]>:
> On Tue, 2008-06-10 at 06:42 +0200, Pavel Stehule wrote:
>> internally is table functions implemenation identical with SRF.
>
> It's not the internals that I'm concerned about.
>
>> Semantically is far - user
2008/6/10 Neil Conway <[EMAIL PROTECTED]>:
> On Tue, 2008-06-03 at 13:03 +0200, Pavel Stehule wrote:
>> this patch add support of table functions syntax like ANSI SQL 2003.
>
> I'm not necessarily opposed to this, but I wonder if we really need
> *more* syntax variant
2008/6/10 Tom Lane <[EMAIL PROTECTED]>:
> Neil Conway <[EMAIL PROTECTED]> writes:
>> On Tue, 2008-06-03 at 13:03 +0200, Pavel Stehule wrote:
>>> this patch add support of table functions syntax like ANSI SQL 2003.
>
>> I'm not necessarily opposed to t
mance with SQL/PSM.
Regards
Pavel Stehule
*** ./doc/src/sgml/ref/create_function.sgml.orig 2007-09-11 02:06:41.0 +0200
--- ./doc/src/sgml/ref/create_function.sgml 2008-06-03 11:50:25.0 +0200
***
*** 21,27
CREATE [ OR REPLACE ] FUNCTION
name ( [ [ argmode ]
2008/5/14 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> I am sending enhanced version of original patch.
>
> Applied with syntax revisions as per pghackers discussion.
thank you
>
> I made a couple of other chan
Pavel Stehule
2008/5/12 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> I am sending enhanced version of original patch.
>
> Hmm ... this patch seems to have been generated against something
> significantly different from HEA
Hello
I am sending enhanced version of original patch.
2008/5/5 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> this patch adds possibility to set additional options (SQLSTATE,
>> DETAIL, DETAIL_LOG and HINT) for RAISE statemen
Hello
I am sending little bit smarter version - without redundant parsing.
When test expression is defined, then expressions in WHEN part are
modified like
$x in ( origin_expression )
$x is referenced to invisible *case* variable that carries result of
test expression.
Regards
Pavel Stehule
Hello
I thing, all your comments are not problem. I'll send new version this week.
Thank You
Pavel Stehule
2008/5/5 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> this patch adds possibility to set additional options (SQLSTATE,
Hello
2008/5/3 Tom Lane <[EMAIL PROTECTED]>:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>> 2008/5/2 Heikki Linnakangas <[EMAIL PROTECTED]>:
>>> How about taking a completely different strategy, and implement the
>>> CASE-WHEN construct
Hello
2008/5/2 Heikki Linnakangas <[EMAIL PROTECTED]>:
> Pavel Stehule wrote:
>>
>> Hello
>>
>> I found some bugs when I used base_lexer, so I returned back own
>> lexer. It's only little bit longer, but simpler.
>
> Hmm. I don't like ha
2008/5/1 H. Harada <[EMAIL PROTECTED]>:
> 2008/5/1 H. Harada <[EMAIL PROTECTED]>:
>> 2008/5/1 Pavel Stehule <[EMAIL PROTECTED]>:
>>
>> > Hello
>> >
>> > why you don't use polymorphic types?
>> Ah, good idea. I didn&#x
Hello
2008/5/1 Jaime Casanova <[EMAIL PROTECTED]>:
> On Sat, Apr 5, 2008 at 6:57 AM, Pavel Stehule <[EMAIL PROTECTED]> wrote:
>> Hello
>>
>> I found some bugs when I used base_lexer, so I returned back own
>> lexer. It's only little bit longer, but si
end loop;
return;
end;
$$ language plpgsql;
Regards
Pavel Stehule
2008/5/1 H. Harada <[EMAIL PROTECTED]>:
> Here's the sync and updated patch.
> It contains "strict" in catalog as well.
>
> Hitoshi Harada
>
> 2008/4/24 H. Harada <[EMAIL PROTECTE
level 'format' [, expression [, ...]] [ USING ( option =
expression [, ... ] ) ];
RAISE EXCEPTION 'Nonexistent ID --> %', user_id
USING (hint = 'Please, check your user id');
Regards
Pavel Stehule
*** ./doc/src/sgml/plpgsql.sgml.orig 2008-04-16 11:17:51.0
b 'WHERE b = $1'
USING b;
RETURN;
END;
$$ LANGUAGE plpgsql;
Regards
Pavel Stehule
*** ./doc/src/sgml/plpgsql.sgml.orig 2008-04-05 12:19:24.0 +0200
--- ./doc/src/sgml/plpgsql.sgml 2008-04-05 12:32:51.0 +0200
***
*** 1451,1457
! RE
Hello
I found some bugs when I used base_lexer, so I returned back own
lexer. It's only little bit longer, but simpler.
Regards
Pavel Stehule
*** ./doc/src/sgml/plpgsql.sgml.orig 2008-04-04 12:07:12.0 +0200
--- ./doc/src/sgml/plpgsql.sgml 2008-04-04 21:55:08.0
Hello
I am sorry, I sent wrong patch, I did diff from generated files.
Current patch set sql features correctly.
Regards
Pavel Stehule
*** ./doc/src/sgml/plpgsql.sgml.orig 2008-04-04 12:07:12.0 +0200
--- ./doc/src/sgml/plpgsql.sgml 2008-04-04 21:55:08.0 +0200
7;;
and case expression
CASE $1
WHEN 1 THEN 1
WHEN 2 THEN 1
WHEN 3 THEN 1
WHEN 4 THEN 2
END;
When result is NULL then it uses 0 path.
Regards
Pavel Stehule
*** ./doc/src/sgml/features-supported.sgml.orig 2008-04-04 14:16:52.0 +0200
--- ./doc/src/sgml/features-supported.sgml
plpgsql. So I can move duplicate parts to separate
files and I'll do it.
I thinking about new directory structure (some like)
pl/sqlsp/ .. sql Stored Procedures
pl/sqlsp/utils
pl/sqlsp/plpgsql - only plpgpsm code
pl/sqlsp/plpgpsm - only plpgsql code
Regards
Pavel Stehule
--
Sent via pgs
Hello
On 01/04/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
> > I actualized sql/psm patch. This patch can be downloaded from
> > http://www.pgsql.cz/patches/plpgpsm.diff.gz
>
> The fundamental problem I&
Hello
On 31/03/2008, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
>
> Pavel Stehule wrote:
>
> > correct queue
> >
> > Hello
> >
> > I finished this patch.
> >
> > Proposal:
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg
and case expression
CASE $1
WHEN 1 THEN 1
WHEN 2 THEN 1
WHEN 3 THEN 1
WHEN 4 THEN 2
END;
When result is NULL then it uses 0 path.
Questions:
a) is possible to use SQL scanner? Now, scanner isn't directly used everywhere.
any notes and comments are welcome
Regards
Pavel Stehu
On 25/03/2008, Zdenek Kotala <[EMAIL PROTECTED]> wrote:
> you have extra space onPavel Stehule napsal(a):
>
> > Hello
> >
> > http://archives.postgresql.org/pgsql-patches/2007-10/msg00161.php
> >
> > I actualized this patch for current CVS
>
>
> Hi Pavel,
>
> I tested your patch and it works r
Hello
http://archives.postgresql.org/pgsql-patches/2007-10/msg00161.php
I actualized this patch for current CVS
Regards
Pavel Stehule
*** ./doc/src/sgml/plpgsql.sgml.orig 2008-03-23 01:24:19.0 +0100
--- ./doc/src/sgml/plpgsql.sgml 2008-03-24 20:41:27.0 +0100
($1,2) g2(j);
$$ language sql immutable;
postgres=# select * from unnest2(array[[1,2],[3,4]]);
unnest2
-
1
2
3
4
(4 rows)
Proposal: http://archives.postgresql.org/pgsql-hackers/2007-10/msg00874.php
Regards
Pavel Stehule
*** ./doc/src/sgml/func.sgml.orig 2008-
Hello
I actualized sql/psm patch. This patch can be downloaded from
http://www.pgsql.cz/patches/plpgpsm.diff.gz
Documentation is on wiki http://www.pgsql.cz/index.php/SQL/PSM_Manual
Regards
Pavel Stehule
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to
On 29/01/2008, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> Am Montag, 28. Januar 2008 schrieb Pavel Stehule:
> > this patch define new function flag - OBFUSCATE. With this flag
> > encrypted source code is stored to probin column. Password is stored
> > in GUC_SUPERUSE
On 28/01/2008, Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>
> > Do you thing some binary module that load some encrypted sources from
> > files? It can be possible too. But if source code will be stored in
>
you thing some binary module that load some encrypted sources from
files? It can be possible too. But if source code will be stored in
pg_proc, then we need third method. Some like "obfuscate" (prev. are
validate and call"), because we can't to store plain text to prosrc
co
On 28/01/2008, Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
>
> >> In such a scheme I think you would put the key in an attribute of the
> >> language. Either in pg_lang or some configuration location which the
On 28/01/2008, Gregory Stark <[EMAIL PROTECTED]> wrote:
>
> Someone along the way suggested doing this as a kind of "wrapper" PL language.
> So you would have a PL language like "obfuscate:plperl" which would obfuscate
> the source code on the way in. Then when you execute a function it would
> deo
On 28/01/2008, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
>
> Pavel Stehule wrote:
> > Hello
> >
> > this patch define new function flag - OBFUSCATE. With this flag
> > encrypted source code is stored to probin column. Password is stored
> > in GUC
On 28/01/2008, Dave Page <[EMAIL PROTECTED]> wrote:
> On Jan 28, 2008 2:26 PM, Pavel Stehule <[EMAIL PROTECTED]> wrote:
> > sure, but do you know, Tom dislikes new columns in pg_proc :).
>
> Tom doesn't seem to like the idea of obfuscation of function code much
>
On 28/01/2008, Dave Page <[EMAIL PROTECTED]> wrote:
> On Jan 28, 2008 12:51 PM, Pavel Stehule <[EMAIL PROTECTED]> wrote:
> > Hello
> >
> > this patch define new function flag - OBFUSCATE. With this flag
> > encrypted source code is stored to p
Hello
this patch define new function flag - OBFUSCATE. With this flag
encrypted source code is stored to probin column. Password is stored
in GUC_SUPERUSER_ONLY item - it is similar security like SQL Server
does (where privileged users can access system tables with source code
or can use debugger)
user to do anything he
> > couldn't
> > before.
>
> I think this feature has value:
>
+1
I thing so is better commit smaller pieces more often than one time
one big patch. Nine months long feature freeze time is enough.
Regards
Pavel Stehule
> (1) This is SQL-standard
sed on Bauman's libraries for MySQL). With this extension we are
able to write some sophistic libraries.
What do you thing about this concept? Has any sense continue in this project?
Regards
Pavel Stehule
postgres=# select json_members('aaa',1,'',20);
json_members
---
Hello
documentation fix.
result of convert_to is bytea, not text.
Regards
Pavel Stehule
*** ./src/sgml/func.sgml.orig 2007-12-12 17:18:55.0 +0100
--- ./src/sgml/func.sgml 2007-12-12 17:19:56.0 +0100
***
*** 1386,1392
convert_to(string text
Wrong address :)
Pavel
On 12/12/2007, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
> While looking at the package function precedence problem, I bumped into
> another unrelated bug:
>
> According to a quick Google search, Oracle doesn't accept DDL in PL/SQL;
> you have to use EXECUTE IMMEDIATE t
Hello
per proposal http://archives.postgresql.org/pgsql-hackers/2007-11/msg01012.php
This patch allows iteration over cursor, so longer SELECTs can be
written outside cycle. Clean some related redundant code too.
Regards
Pavel Stehule
forc.diff.gz
Description: GNU Zip compressed data
Hello
this patch add anyelement variants of functions quote_literal and
quote_ident. Changes of casting rules in 8.3 has impact on these
functions, but there is same situation like operator ||. Is clear so
arguments is string or have to cast to string.
Regards
Pavel Stehule
*** ./src/include
On 13/11/2007, Tom Lane <[EMAIL PROTECTED]> wrote:
> I wrote:
> > I've modified Pavel's version into something that seems to support this
> > approach --- at least I can load the 8.2 tsearch regression test
> > database into 8.3 after loading this. Still needs some polishing
> > probably, and some
On 10/11/2007, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
> > I found different problem, that have to be solved if wrapper have to
> > be dump compatible.
>
> > there is about five functions with same name, a
On 10/11/2007, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
> > On 10/11/2007, Tom Lane <[EMAIL PROTECTED]> wrote:
> >> * The SQL file doesn't create any of the old types (public.tsvector
> >> etc)
Hello
On 10/11/2007, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Pavel Stehule" <[EMAIL PROTECTED]> writes:
> > this is revised version
>
> A couple of thoughts here:
>
> * What is the point of creating stub functions for things that users
> won'
On 09/11/2007, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > A thought on this - should it not go in contrib/tsearch2 replacing the old
> > deprecated stuff, instead of creating yet aother contrib dir?
It can be moved - no problem.
>
> That was the idea,
wait two days, please.
Pavel
I'll send finished patch on Sunday.
On 09/11/2007, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> Should I apply this or wait for a final version?
>
> -------
>
> P
Hello
I am sending light wrapper of integrated fulltext. API is compatible
with tsearch2.
Regards
Pavel Stehule
ToDo: rewrite functions
diff -c -N -r contrib.old/tsearch2api/Makefile contrib/tsearch2api/Makefile
*** contrib.old/tsearch2api/Makefile 1970-01-01 01:00:00.0 +0100
> >
> > Any thoughts?
>
> I think a prefix of ':' would be good, as it's already a standard,
> kinda. Anybody who names a database object :foo deserves whatever
> happens to them :P
>
> Cheers,
> David.
+1
':' is shorter than 'this'. And ':' is well known in SQL area.
Pavel
---
insert into t values(10,20);
create function foo(a integer)
returns integer
as $$
select a from t
where a <> b and a = 10;
$$ languge sql;
select foo(20);
output? expected 10, but you will get NULL!
Regards
Pavel Stehule
so some prefixes can help
create function foo(a integer)
returns inte
uages.
It can be more wide used:
* named params in prepared statements
* named params in SPI
* ..
Regards
Pavel Stehule
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command t
Hello
I am sendin actualised czech FAQ. It was updated, encoded to utf8 and
checked by spellckecker
Regards
Pavel Stehule
actualised_czech_faq.diff.tar.gz
Description: GNU Zip compressed data
---(end of broadcast)---
TIP 1: if posting/reading
2007/10/23, Heikki Linnakangas <[EMAIL PROTECTED]>:
> Pavel Stehule wrote:
> >> This doesn't work:
> >>
> >> create function exc_using(varchar) returns varchar
> >> as $$
> >> declare v varchar;
> >> begin
> >>
>
> This doesn't work:
>
> create function exc_using(varchar) returns varchar
> as $$
> declare v varchar;
> begin
> execute 'select upper($1)' into v using ('aa');
it cannot work. Your parameter is row. But
into v using 'aaa' doesn't work too :(
ERROR: failed to find conversion function from
ger, and I need to know any responsible
person who can be recipient of my reminder request. Really it's
nothing nice, if your work is repeatedly deleted or inserted to
current queue. Nobody can do any plans.
Best regards
Pavel Stehule
*** ./doc/src/sgml/plpgsql.sgml.orig 2007-10-22 10:31:57.
Hello
New version of SQL/PSM patch is available. I am sending only link,
because mail with attached patch was lost. Documentation is on
available from http://www.pgsql.cz/index.php/SQL/PSM_Manual
http://www.pgsql.cz/patches/plpgpsm83.diff.gz
Regards
Pavel Stehule
tested it. It's great. Thank You
Pavel Stehule
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
OPEN statement. Refcursors are problematic. But refcursors
are not updatable.
We have to check this case and raise error. It's correct - holdable
cursors aren't updatable. It's WIP patch
Regards
Pavel Stehule
---(end of broadcast)-
2007/6/11, Tom Lane <[EMAIL PROTECTED]>:
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> this small patch allows using updatable cursors in plpgsql.
Why do we need this?
For stored procedures. Updatable cursors are used mainly in transform
procedures, and without supp
Hello,
this small patch allows using updatable cursors in plpgsql.
Regards
Pavel Stehule
*** ./gram.y.orig 2007-06-11 10:43:09.0 +0200
--- ./gram.y 2007-06-11 11:48:03.0 +0200
***
*** 44,49
--- 44,50
static void plpgsql_sql_error_callback(void *arg
Hello
this patch removes unsupported switch u from description for command.
Regards
Pavel Stehule
*** ./contrib/pg_standby/pg_standby.c.orig 2007-05-22 15:47:42.0 +0200
--- ./contrib/pg_standby/pg_standby.c 2007-05-22 15:48:10.0 +0200
***
*** 379,385
fprintf
teable cursors.
I am for it. It good protection before strange bugs
Pavel
Rgds,
Arul Shaji
Pavel Stehule wrote:
> 2007/5/18, FAST PostgreSQL <[EMAIL PROTECTED]>:
>> No. It works with scrollable cursors. It will work for cursors/selects
>> which does not put the results
east a pass mark :-)
Rgds,
Arul Shaji
Pavel Stehule wrote:
> Hello
>
> I am not sure, but your solution will faill on scrollable cursors
> (it's similar to holdable cursors). I miss part about limits in
> documentation. Propably updatable cursors aren't supported by plpgsq
Hello
I am not sure, but your solution will faill on scrollable cursors
(it's similar to holdable cursors). I miss part about limits in
documentation. Propably updatable cursors aren't supported by plpgsql
(and it's point to ToDo).
Regards
Pavel Stehule
2007/5/17, FAST Pos
Do we have a patch to make this consistent?
no, not yet. It's topic for discussion and ToDo
Regards
Pavel Stehule
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail comma
ression is clean and simple tool for it.
Older version was broken by enum patch and scrollable cursor patch.
Older version didn't dump table functions correctly. It's fixed now.
Regards
Pavel Stehule
*** ./pg_dump.c.orig 2007-05-06 11:13:11.0 +0200
--- ./pg_dump.c 2007-
Hello,
I actualised sql/psm patch:
added:
* last Tom's plpgsql patches (some fixes and enum support)
* scrollable cursor's support
new version is on http://www.pgsql.cz/patches/plpgpsm0501.diff.gz
Regard
Pavel Stehule
Your patch has been added to the PostgreSQL unapplied patch
than MOVE RELATIVE 10 and if we support
MOVE FORWARD ... then is logic support MOVE FORWARD n ,
else FORWARD, BACKWARD are nonstandard and MOVE statement too.
Regards
Pavel Stehule
_
Citite se osamele? Poznejte nekoho vyjmecn
Hello
I refreshed Magnus's patch
http://archives.postgresql.org/pgsql-patches/2007-02/msg00275.php from
februar.
Regards
Pavel Stehule
p.s. scrollable cursors in plpgsql need little work still. I forgot for
nonstandard (postgresql extension) direction forward all, forward n,
backw
On Wed, 2007-03-28 at 17:42 +0200, Pavel Stehule wrote:
> >
> >This is the most recent email I have on this. Was the scrollable patch
> >applied? If not, would you resubmit?
> >
>
> I resubmit scrollable cursor patch
I notice your patch has been accepted, th
NEDM.Chapter.03.User-defined_Routines_and_Object_Behavior.pdf
Regards
Pavel Stehule
From: Tom Lane <[EMAIL PROTECTED]>
To: "Pavel Stehule" <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: [PATCHES] Table function support Date: Tue, 10 Apr 2007
18:17:14 -0400
"Pa
ision, and x,
and y are table attributies (not variables) and then we are protected before
collision. It's shortcut for
create function foo() returns setof record as ...
select * from foo() as (x int, y int);
Regards
Pavel Stehule
ision, and x,
and y are table attributies (not variables) and then we are protected before
collision. It's shortcut for
create function foo() returns setof record as ...
select * from foo() as (x int, y int);
Regards
Pavel Stehule
-superuser sessions, which is surely not desirable.
I don't protect this patch. I didn't understand original proposal well.
Tom, I don't understand your last notice. Can you explain it, please.
Pavel Stehule
_
Citite se
ion where I can safely modify
custom variables.
---
>
> Regards
> Pavel Stehule
>
>
> >From: Bruce Momjian <[EMAIL PROTECTED]>
> >To: Pavel Stehule <[EMAIL PROTECTED]>
> >
value.
Regards
Pavel Stehule
From: Bruce Momjian <[EMAIL PROTECTED]>
To: Pavel Stehule <[EMAIL PROTECTED]>
CC: pgsql-patches@postgresql.org, [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [PATCHES] simply custom variables protection
Date: Sat, 7 Apr 2007 11:54:13 -0400 (EDT)
Pavel, wo
://archives.postgresql.org/pgsql-hackers/2007-03/msg01487.php
link to patch: http://www.pgsql.cz/patches/plpgpsm.diff.gz
Regards
Pavel Stehule
_
Chcete sdilet sve obrazky a hudbu s prateli? http://messenger.msn.cz
This is the most recent email I have on this. Was the scrollable patch
applied? If not, would you resubmit?
I resubmit scrollable cursor patch
Regards
Pavel Stehule
_
Emotikony a pozadi programu MSN Messenger ozivi vasi
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> this patch contains function ArmorCustomVariables. This function set
flag
> armored on any custom variable. From this moment only superuser can
change
> this variable.
Why is this a good idea? Why don't you just
1 - 100 of 216 matches
Mail list logo
